In this lab exercise, you are going to try running your tests on another team's
BooksDataSource.
Running the tests
- Make sure you're sitting with your team, and that one member of your team has a laptop
ready for running Python.
- Make sure your git repository is all up to date: committed, pulled, pushed, etc.
- Identify another team to work with (ideally, a team sitting at your table). If three
teams want to get together, that's fine.
- Share your booksdatasource.py file with the other team. You can do this via Slack direct message,
adding the other team as a collaborator on your GitHub repository, email attachment, or whatever.
- Copy your Makefile, your booksdatasourcetest.py, and the other team's booksdatasource.py into
a temporary working directory. In that directory, run "make test".
- Do the tests run without crashing? Does the other team's BooksDataSource pass your tests?
You won't know until you try. Work with the other team to resolve any problems getting
the tests to run, and then put together the report below.
What to hand in
NOTHING!
That said, the rest of this section is what I asked last year's class to hand in. It's worth
seeing what I wanted you to get out of the exercise.
Create a text file called test-results.txt in your books directory. To be clear, you will
be providing a report on the results when you ran your tests on somebody else's
BooksDataSource implementation. When you're done writing this report, add it to your repository,
commit it, and push it. Do as much as you have time for in class today, and then don't worry
about it after that. This will be a 5-point "did you do it at all?" assignment, where you get
the points if you showed up and did the basic thing with the time allotted.
(For the students at the Grace Hopper conference, you can ask another team for their
booksdatasource.py after you get back, and write your test-results.txt by Oct 5.)
Here's what should go in test-results.txt.
- A title: "BooksDataSource Test Results, 21 September 2018"
- The names of the people on your team
- The names of the people on the other team
- Did the other team's code pass their own tests? (This is a short-answer question, and you
can find out by just asking them.)
- A brief description of how the compilation and runnning process went.
If you had to modify anything, fix any function-calling mismatches, etc., tell
me about it here.
- For each of the test methods in your BooksDataSourceTest class:
- Name of the test method
- Did it pass or fail?
- If it failed, why? Was it a bug in the other team's books_for_author?
A bug in the test itself? (Yes, sadly, tests can have bugs, too.)
A disagreement between the teams on how to
interpret the specification (which might also reflect a failure of clarity
in the spec)? Something else?