How to Create a Test Case

[edit] How to Create a Test Case

Date of updated session: April 2, 2009
Presenters of the updated session: Matthias Leich, Bernt Johnsen, Patrick Crews
To attend, point your browser to this address. Note that the meeting room will open only 15 minutes before the hour.

Why isn't the repository containing the extra tests part of the regular BK source tree?
- One concern was to keep the regular trees from getting too big.
Can the repository be made public?
- Yes, it could be.
Can you point to any specific bug being discovered by upgrade/downgrade testing?
- Yes, we discovered a change in the INFORMATION_SCHEMA structure where extra columns were added that caused problems for a downgrade to a version that didn't know about the extra columns.
How many tests are run in the concurrency tests?
- Fifty concurrent clients for 24 hours. (The clients start, run their tests, exit, and repeat.)
- Another test has 2000 concurrent clients.
Do you test for deadlocks specifically?
- No, but they can happen for randomly generated tests, and we try to identify when they do.
- We try to identify other kinds of problems as well. For example, if the server says a table needs repair, we tell it to repair the table, then stop and restart the server before restarting the test.
You say uppercase for SQL keywords, but almost all of the existing tests are completely lowercase. This seems to be a guideline almost never followed?
- Use the uppercase style for new test cases. Existing test cases that use lowercase should be left in that style, in general.
"OS command" is what? exec and system?
- Both.

Session recording (video/audio) of the updated session: here (unfortunately, Dimdim lost the audio track, so it's just the slides).
Chat transcript of the updated session: here.

This page has been accessed 7,317 times. This page was last modified 13:38, 3 April 2009.