The following is an extract from a fault log, write down any potential problems or omissions with this:
[
]
Answer:
Potential Problems/Omissions
.. No date on log as to when raised
.. No keywords (i.e. screen) so that searches can be performed preventing duplication of fault logs
.. No status of the log (opened/fixed/closed/cleared etc.)
.. No owner of the log. .. Has priority – but no severity (i.e. risk to the customer)
.. No version number of the system being tested – it is very likely that the testers are on a different version to development and that it was a fault but has been inadvertently fixed on this latest software
.. Query the priority of this log (should it be a 3?)
.. No actual error message on the log – this may give some clue to the developer about the nature of the fault
.. Response seems to be leading to a dialogue – if we are not careful this fault will never be fixed! Tester should talk to the developer rather than sending another message via the fault log.
.. The response by the developer points to another part of the system (security) – this may be an indication of developers trying to quickly close the issue without performing sufficient investigation. It could however be because the tester has not spent enough time documenting the problem.
By Grove Consultants
Choose your rating:
Post Ans. View More Ans.
An ATM has been specified to work in the following way ....
[
]
An ATM has been specified to work in the following way:
Enter a card and if the card is invalid reject the card and exit system. If it is a valid card then enter a PIN number. Check to see if the PIN is invalid
– if it is then display a message ‘invalid pin number, please re-enter’. If 3 attempts are made with an invalid pin then the machine keeps the card. If it is a valid PIN then the user can select one of the following transactions:
• Cash Withdrawal without receipt
• Cash Withdrawal with receipt
• Balance Enquiry
• Statement request
• Cancel
What tests would you produce to test this application? State any assumptions when testing
Answer:
1. Invalid Card – reject card and exit
2. Valid Card and Invalid PIN – error message ‘invalid pin…’ (then enter valid pin)
3. Valid Card and Invalid PIN – error message ‘invalid pin…’ (then enter another 2 invalid Pins)
4. Valid Card, Valid Pin & Cancel (correct length pin)
5. Valid Card, Valid Pin in a large number – but the pin number contains more than the maximum number – should error
6. Valid Card, Valid Pin & Cash Withdraw without receipt
7. Valid Card, Valid Pin & Cash Withdraw with receipt
8. Valid Card, Valid Pin & Balance enquiry
9. Valid Card, Valid Pin & Statement Request
10. Destructive tests include:
• Putting in 2 cards • Putting correct pin, but adding an extra number to make invalid Assumptions:
1. Can insert up to 3 invalid pins and machine retains card
2. Can only select one transaction and then have to re-insert card
3. Pressing cancel will return card
Choose your rating:
Post Ans. View More Ans.
Choose which program you would re-test and state you reasons? ...
[
]
Scenario:
You are testing 2 programs and have 3 weeks to test them both. Having run all of your tests on both programs you finish testing within 2 weeks. You need to decide which of the 2 programs you would re-visit and run further tests against. Choose which program you would re-test (can choose only one!) – and state you reasons:
Program A
Programmer:
A Complexity Level: 2
Lines of Code: 2000
Number of tests: 100
Number of bugs found: 10
1 high severity, 3 medium & 6 low)
Program B
Programmer:
B Complexity Level: 2
Lines of Code: 2000
Number of tests: 100
Number of bugs found: 50 (10 high severity, 25 medium & 15 low)
Answer:
Key points:
1. Different programmers wrote A and B
2. Complexity level of the programs are the same
3. Size of the programs are the same
4. Tester is the same for testing A and B
5. Number of tests run on both programs is the same
6. Number of bugs is higher in program B
Program B seems to have far more faults therefore we would be inclined to spend the further week testing Program B, as there is likely to be more bugs to find. We may also not be very confident at this point with Program B therefore we need to see our confidence increased.
Choose your rating:
Post Ans. View More Ans.
How would you prioritise your tests (list 5)?
[
]
Answer:
• ask the customer to prioritise the requirements
• ask the customer to prioritise the tests
• what is most critical to the customer’s business
• test where a failure would be most severe
• test where failures would be most visible
• test where failures are most likely
• areas changed most often
• areas with most problems in the past
• most complex areas, or technically critical
Choose your rating:
Post Ans. View More Ans.
Write a set of test cases to adequately test this telephone system ...
[
]
A hotel telephone system can perform 3 functions:
• Call another hotel room by entering a room number (201 to 500)
• Call an external line by entering a 9, followed by the number
• Call various hotel services
• 0 = Operator
• 7 = Room Service
• 8 = Reception
Write a set of test cases to adequately test this telephone system
Positive/Valid Tests
Input Expected Result
----------------------
0 Operator
201 Room 201 (valid boundary)
405 Room 405 (valid partition)
500 Room 500 (valid boundary)
7 Room Service
8 Reception
9 Outside line
Negative/In-valid Tests
Input Expected Result
--------------------------
1 Error
6 Error
200 Error (invalid boundary)
501 Error (invalid boundary)
550 Error (invalid partition)
Any other button Error
Destructive Tests
What if I accidentally hit multiple buttons?
What if I entered an 0800 number without first
getting an outside line (operator should answer)
Choose your rating:
Post Ans. View More Ans.
Why do you consider testing to be necessary?
[
]
.. There are faults in the software
.. Failures in live operation can be expensive
.. Sometime a ‘legal’ or contractual requirement
.. To asses the quality of the software
.. To preserve the quality of the software
.. To help achieve quality software (by finding and removing the faults)
Choose your rating:
Post Ans. View More Ans.
How would you test these requirements:
[
]
a) The system must be user-friendly
b) The system must be easy to install
c) The following response times are to be achieved with the new system:
• Initial loading of the web application must be achieved within 3 seconds
• Updating of the information on the web page must be no more than 5 seconds
Answer:
How would you approach these requirements:
a) The system must be user-friendly
What do we mean by ‘user-friendly’? Questions to ask:
.. Friendly to whom?
.. Who are the users?
Test approaches:
.. Talk to the users
.. Document assumptions
.. Compile test scenarios for people who have not seen the system
b) The system must be easy to install
What do we mean by ‘easy? Questions to ask:
.. For whom? ..
Is there any installation documentation to follow?
Test approaches:
.. Follow installation documentation (if there is any)
.. Allow tests to be run by an inexperienced user to see how easy it is
.. Document tests and review these with the users
c) The following response times are to be achieved with the new system:
• Initial loading of the web application must be achieved within 3 seconds
• Updating of the information on the web page must be no more than 5 seconds
Once more we need to ask some probing questions surrounding this requirement:
.. What happens if we don’t meet the times?
.. Would a range of values be better?
.. What is happening on the network?
.. Are these average times or are they ‘peak’ times?
.. What is involved in updating – how much information?
In attempting to test this requirement we would document the exact criteria for the test and the simplest way would be to time a number of tests and supply the average.
With all these 3 requirements, what we are looking for is to see whether the potential tester will challenge the requirements of whether they would just accept them and try to test to the best of their ability
Choose your rating:
Post Ans. View More Ans.
Name 2 standards that refer to testing
[
]
Any of the following:
BS 7925-1 (Glossary of testing terms), BS7925-2 (Component Testing), ISO9000 and ISO9001 (Quality standards), IEEE829 (Test Documentation), IEEE1028 (Reviews), IEEE1044 (Incidents)
Choose your rating:
Post Ans. View More Ans.
List 3 test tool categories and describe what each can do.
[
]
Answer:
.. Test Design Tools
.. Test Data Preparation Tools
.. Regression Testing tools
.. Debug Tools
.. Dynamic Analysis Tools
.. Coverage Measurement Tools
.. Static Analysis Tools
.. Performance Testing Tools
.. Test Management Tools
.. Network monitoring tools
.. Test Harness or Simulation tools
The importance of this question is to see if the candidate has any knowledge about tools. We do not want the names of tools but want to know if the candidate can distinguish between the types of tool.
Choose your rating:
Post Ans. View More Ans.
Do you consider testing tools to be valuable during the testing process why/why not?
[
]
Testing tools are very important to assist the tester in their work. Using tools can also potentially make the tester more efficient in their work – they are able to run more tests (using regression testing for example). Or they can quickly compare 3 reports (comparison tool).
The tools in themselves however do not make good testers and also should not be considered if the test process is in ‘chaos’.
Choose your rating:
Post Ans. View More Ans.
