Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
6 Cards in this Set
- Front
- Back
|
I don't have to test in the latest build before I enter a bug for development. |
False: You should always use the latest build to test, as code is being developed daily. |
|
|
I don't need to get a copy of the customer database. |
False: The customer database is required to properly duplicate and resolve an entered bug. |
|
|
I need to know how to re-create all the steps to duplicate a bug item. |
True: You must be able to duplicate all the steps in a bug so development can target the correct code. |
|
|
I entered a bug this morning, so it should be fixed by this afternoon, correct? |
False: The bugs are assigned a point value, and will be prioritized according to the point value. If a bug is not critical, then it will go through the triage meeting process at 1:30 pm. |
|
|
I have already talked to the developer and they are working on the issue; can't you just push my item through? |
Nope: Even though the developer knows about your item, it still needs to be documented in a way which meets the needs of QA for duplication and development for testing. You must still fill out the bug in TFS with all the requirements of any bug item. |
|
|
If the customer is moving from an old build to a current release, should I still put in a bug for the old release? |
It is advised you test in the new release version to verify the bug is still an issue and enter the bug on the newer release. |
