I am relatively new in testing and about to embark on my first project. I have been sent the requirement to the project and the first meeting is comming up soon.
1. What kind of questions can I ask at this meeting?
2. The project is on cv management and some of the reqts include:
-> personal information e.g Name, Title, hobbies
-> school attended with dates
How do I generate my testcases from the info supplied or betterstill where do I go from here.
Thanks for your input
You first need to fully understand the requirement, so review it carefully and come to the meeting with questions about things you might not fully understand. Once you understand the requirement, you can begin creating test cases.
When creating test cases, you should create "positive test cases". These are test cases that test the features as they were designed (i.e. Check grammar, ensure it adds/edits/delete records correct, creates audits (if necessary), etc.
Also create "negative test cases". These are test cases that use the system in ways it was not designed. For example, try putting a date of February 30 in, does it give a friendly message for that. Create test cases for bounds (if a field can only be between 1 and 100, try 0 and 101). For more info on negative test cases, see this whitepaper: http://www.softwareplanner.com/Newsl...007_09_SP.htm.
What I would normally do for requirements and this is for me personally is to read through the document/s with a highlighter in one hand and highlight:
1/ Anything that is unclear.
2/ Anything that I cant understand.
3/ Anything that is not testable.
4/ Any 'fuzzy' requirements (requirements like 'system should demonstrate acceptable response times'..what is acceptable? or 'the system should be w3c compliant'..should? does that mean it will or it wont be)
5/ Are non functional requirements defined.
and many more things...if you need more then google requirements checklists this will give you several examples.
I would then list all these issues as review comments to be clarified. Then looking at all the areas that are testable I would put them all into a mind map and list how these will be tested as a single page summary of everything I would aim at doing.
Move the ways that you would test the testable requirements into a spreadsheet and you have the tests that you can run so far. To go any further in establishing test cases you will need to know what technical solutions are and how they are delivering features to you from development.
If they are delivering software in a big bang then prioritise your tests and establish cycles you will run and you are sorted. If they are delivering the features of the software iteratively (several staggered deliveries over a period of time) then the tests can be broken up in to the features that are delivered with each iteration and prioritised per iteration forming several test cases.