Convert Orphan OST to PST With Tool to Repair OST Database
The business requirement stated the list Newscaster
Vocalizer Review of screens pertaining to the withdrawal and Balance Inquiry modules for which this requirement was supposed to be implemented. On analysis, this requirement was impacting more places like the screen in which the user checks out the history of transactions, or does a deposit, or sets up a standing instruction to the bank. On discussing the issue with the client, it was found that they thought that this was implied.
This is the continuation from the previous point that as a tester it is very important that you should not assume any of the requirement/issues/problems/defects. For example, never assume that in a screen where data has captured a field labeled Clear clears the entire content, though it is pretty evident. Ask more questions and get the affirmations from the respective persons. Also, remember that it is necessary to test the software from the end user's perspective and not just compliance with the requirements given by the client.
It is a skill to convince and explain to a person who has developed the software as to why a defect report is written is indeed a defect. Put forth this in such a way that the developer also starts thinking along the lines of the scenario given in the defect report/requirement. Remember in such situations to put you in other person's shoes and speak accordingly. Avoid using accusing words, do not get into any arguments and do not rise to any bait a developer may throw at you. Concentrate on the issue and not on the person.
Also, while deciding the end of testing activities, it is important to bring out the impact of the open defects in the software and the implications to the business analyst/client or whoever is the logical endpoint contact. It is necessary to push your point through either to continue with further testing activities or to stop testing.
This is the continuation from the previous point that as a tester it is very important that you should not assume any of the requirement/issues/problems/defects. For example, never assume that in a screen where data has captured a field labeled Clear clears the entire content, though it is pretty evident. Ask more questions and get the affirmations from the respective persons. Also, remember that it is necessary to test the software from the end user's perspective and not just compliance with the requirements given by the client.
It is a skill to convince and explain to a person who has developed the software as to why a defect report is written is indeed a defect. Put forth this in such a way that the developer also starts thinking along the lines of the scenario given in the defect report/requirement. Remember in such situations to put you in other person's shoes and speak accordingly. Avoid using accusing words, do not get into any arguments and do not rise to any bait a developer may throw at you. Concentrate on the issue and not on the person.
Also, while deciding the end of testing activities, it is important to bring out the impact of the open defects in the software and the implications to the business analyst/client or whoever is the logical endpoint contact. It is necessary to push your point through either to continue with further testing activities or to stop testing.
Comments
Post a Comment