Level 3: Test script with cosmetic errors / suggestions
4. How to prevent Test Script/Test Case Defects?
Before the testing phase begins, all test script documents (amongst other documents) should be subjected to formal reviews to prevent the above issues appearing during the formal testing phase. If at all possible, there should be a “dry-running” of the scripts before the formal test execution begins. This gives the testers a chance to raise any uncertainties or doubts about the nature of the scripts and to minimize the number of issues listed above.
Also testers writing the test scripts must have a thorough understanding of the applications and workflows in order to write effective test cases and to maximize the exposure of defects.
Reviewing Test Cases
Subscribe the QA and Software Testing Newsletter Post Your Queries | QA and Testing - Table of Contents
SPONSORED LINKS
The main reason of the reviewing: increase test cases quality and therefore product quality.
As we know testers are involved on the Requirements Specification review process to provide the SQA knowledge to the requirements written. As testers are involved on the process they become experts on the area and on the application functionality and many times their knowledge helps avoid introducing future defects into the functionality that later the developer will code (it’s the phase that we called: defect prevention).
Once the requirements are approved and baselined, testers start designing test cases whether on their mind, or writing them (test drafts). Once all the ideas or test case drafts are understood and prepared, the SQA tester will start developing test cases. When this happens, each test case written is based on a specific requirement, so with that we start assuring having traceability between requirement and test cases. This will help SQA team to manage the Requirements coverage of what is going to be tested.
Once the test cases are developed, SQA tester should share-distribute-discuss those with the same team that reviewed the requirements (SRS writer, Developers, SQA tester,
Implementation team, etc). However, sometimes this is not possible, as perhaps when the
Requirements are baselined, the person who is in charge of the SRS starts on another project and has not even more time to dedicate reviewing a set of test cases. The same happens with the Implementations team, as they are perhaps installing the product on a customer site. There are cases where SQA tester and developer start more or less at the same time with their work based on the Requirements. Developer starts developing code and Tester developing test cases. There are other times that SQ Tester starts thinking or having test case drafts even before the Developer starter coding. That means that developing code and test cases are and should be separate processes.
Of course that having a Requirements-Usability people reviewing test cases has a lot of value, also having the implementations team doing the same. The problem has been that these often did not happen due the lack of resources, so the test cases review would progress only with the developer involved on the same project and functionality. In any case the developer review test cases always would go in the direction
of adding details, parameters or circumstances not included in the tester written test cases or well even adding new test cases but never modifying the sense of the test cases written by the tester.
This is the approach and the how the test cases defined by testers need to be reviewed by the developer.
We should also notice that some times when the test cases writer is a beginner, not a senior tester, or well does not have so much knowledge about the functionality, then someone from the SQA team with more experience should check the test cases before sharing them with the developer for review.
Benefits of having test cases reviews for SQA test cases written, including on them the developers:
• Defect prevention while SRS review: SQA tester could advance during SRS reviews possible issues before any code starts
• Conceptual and Technical Coverage: Requirements- Usability ensures the coverage from the Concept point of view and Developer ensures the coverage from the Technical Point of view. The traceability coverage track is assumed by traceability tools (Quality Center)
• Defect prevention while test cases review: If the developer has the opportunity to check the test cases while implementing code, it is possible that this will help him to realize codification that may be a cause of a defect. This will help to coding in the way of potential defects.
• Developer Knowledge add to test cases: Developer has also a very good understanding of the requirement (SRS), explicit and implicit as well. Also has done a deep analysis of them since he had to accomplish the SRA. He can bring experience on understanding better details or well some cases not being considered.
After having the test cases reviewed, the SQ team receives all the feedback and decides, based on its experience and knowledge on SQA and also on the functionality if feedback is applied or not. When not applied, the reason should be explained and discussed with the developer since there should be a final agreement on the test cases written.
How to write test cases for use cases ? Subscribe the QA and Software Testing Newsletter Post Your Queries | QA and Testing - Table of Contents
SPONSORED LINKS
What is a Use Case?
A use case describes the system’s behavior under various conditions as it responds to a request from one of the users. The user initiates an interaction with the system to accomplish some goal. Different
sequences of behavior, or scenarios, can unfold, depending on the particular requests made and conditions surrounding the requests. The use case collects together those different scenarios.
Use cases are popular largely because they tell coherent stories about how the system will behave in use.
The users of the system get to see just what this new system will be and get to react early.
In software engineering, a use case is
1. A technique for capturing the potential requirements of a new system or software change.
2. Each use case provides one or more scenarios that convey how the system should interact with the end user or another system to achieve a specific business goal.
3. Use cases typically avoid technical jargon, preferring instead the language of the end user or domain expert.
4. Use cases are often co-authored by software developers and end users.
By definition of use cases , we just follow the requirement document so we concentrate of testing like functionality testing
acceptance testing Alpha testing etc
How many User Acceptance Test Cases need to be prepared for an application?
Subscribe the QA and Software Testing Newsletter Post Your Queries | QA and Testing - Table of Contents
SPONSORED LINKS
For testing projects if we know the development effort in FP then there is a rule called Caper Jones rule it says # of test cases = (Function Points) power 1.2
This will give the no. of user acceptance test cases can be prepared.
Software testing Metrices - Test Case Review Effectiveness Subscribe the QA and Software Testing Newsletter
Post Your Queries | QA and Testing - Table of Contents
SPONSORED LINKS
Metrics are the means by which the software quality can be measured; they give you confidence in the product. You may consider these product management indicators, which can be either quantitative or qualitative. They are typically the providers of the visibility you need.
The goal is to choose metrics that will help you understand the state of your product.
Metrics for Test Case Review Effectiveness:
1. Major Defects Per Test Case Review 2. Minor Defects Per Test Case Review 3. Total Defects Per Test Case Review
4. Ratio of Major to Minor Defects Per Test Case Review 5. Total Defects Per Test Case Review Hour
6. Major Defects Per Test Case Review Hour
7. Ratio of Major to Minor Defects Per Test Case Review Hour 8. Number of Open Defects Per Test Review
9. Number of Closed Defects Per Test Case Review 10. Ratio of Closed to Open Defects Per Test Case Review 11. Number of Major Open Defects Per Test Case Review 12. Number of Major Closed Defects Per Test Case Review 13. Ratio of Major Closed to Open Defects Per Test Case Review 14. Number of Minor Open Defects Per Test Case Review 15. Number of Minor Closed Defects Per Test Case Review 16. Ratio of Minor Closed to Open Defects Per Test Case Review 17. Percent of Total Defects Captured Per Test Case Review 18. Percent of Major Defects Captured Per Test Case Review 19. Percent of Minor Defects Captured Per Test Case Review
20. Ratio of Percent Major to Minor Defects Captured Per Test Case Review 21. Percent of Total Defects Captured Per Test Case Review Hour
22. Percent of Major Defects Captured Per Test Case Review Hour 23. Percent of Minor Defects Captured Per Test Case Review Hour
24. Ratio of Percent Major to Minor Defects Captured Per Test Case Review Hour 25. Percent of Total Defect Residual Per Test Case Review
26. Percent of Major Defect Residual Per Test Case Review 27. Percent of Minor Defect Residual Per Test Case Review
28. Ratio of Percent Major to Minor Defect Residual Per Test Case Review 29. Percent of Total Defect Residual Per Test Case Review Hour
30. Percent of Major Defect Residual Per Test Case Review Hour 31. Percent of Minor Defect Residual Per Test Case Review Hour
32. Ratio of Percent Major to Minor Defect Residual Per Test Case Review Hour 33. Number of Planned Test Case Reviews
34. Number of Held Test Case Reviews 35. Ratio of Planned to Held Test Case Reviews 36. Number of Reviewed Test Cases
37. Number of Unreviewed Test Cases
38. Ratio of Reviewed to Unreviewed Test Cases 39. Number of Compliant Test Case Reviews 40. Number of Non-Compliant Test Case Reviews
41. Ratio of Compliant to Non-Compliant Test Case Reviews 42. Compliance of Test Case Reviews
43. Non-Compliance of Test Case Reviews
44. Ratio of Compliance to Non-Compliance of Test Case Reviews
Test Case for an Elevator
Subscribe the QA and Software Testing Newsletter Post Your Queries | QA and Testing - Table of Contents
SPONSORED LINKS
Some of the use cases would be:
1) Elevator is capable of moving up and down.
2) It is stopping at each floor.
3) It moves exactly to that floor when corresponding floor no is pressed.
4) It moves up when called from upward and down when called from downward.
5) It waits until 'close' button is pressed.
6) If anyon steps inbetween the door at the time of closing, door should open.
7) No break points exists
8) More usecases for the load that the elevator can carry (if required) ADDITIONAL:
1) When I push the call button, does it come to the floor and open the door after stopping?
2) Do the doors stay open for at least 5 seconds?
3) When closing, do the doors reverse if someone is standing in their way?
4) Does the elevator wait for someone to push a floor button before moving?
5) Does the elevator ignore the floor button of the current floor?
6) Does the floor button light up when pressed?
7) Does the Open Door button work when the elevator is moving?
8) Does the elevator travel in a smooth fashion?
9) Is there an up button on the top floor or a down button on the bottom floor?
Four Test Cases on ATM, Cell Phone, Traffic Signal, Elevator – Frequently Discussed in Interviews on Software Testing
Subscribe the QA and Software Testing Newsletter Post Your Queries | QA and Testing - Table of Contents
SPONSORED LINKS
Test Case on ATM:
TC 1:- successful card insertion.
TC 2:- unsuccessful operation due to wrong angle card insertion.
TC 3:- unsuccessful operation due to invalid account card.
TC 4:- successful entry of pin number.
TC 5:- unsuccessful operation due to wrong pin number entered 3 times.
TC 6:- successful selection of language.
TC 7:- successful selection of account type.
TC 9:- successful selection of withdrawal option.
TC 10 :- successful selection of amount.
TC 11:- unsuccessful operation due to wrong denominations.
TC 12:- successful withdrawal operation.
Tc 13 :- unsuccessful withdrawal operation due to amount greater than possible balance.
TC 14 :- unsuccessful due to lack of amount in ATM.
TC 15 :- unsuccessful due to amount greater than the day limit.
TC 16 :- unsuccessful due to server down.
TC 17 :- unsuccessful due to click cancel after insert card.
TC 18:- unsuccessful due to click cancel after insert card and pin no.
TC 19:- unsuccessful due to click cancel after language
selection,account type selection,withdrawal selection, enter amount
Difference between CMM and CMMI
Subscribe the QA and Software Testing Newsletter Post Your Queries | QA and Testing - Table of Contents
SPONSORED LINKS
Capability Maturity Model (CMM): A five level staged framework that describes the key elements of an effective software process. The Capability Maturity Model covers practices for planning, engineering and managing software development and maintenance.
Capability Maturity Model Integration (CMMI): A framework that describes the key elements of an effective product development and maintenance process. The Capability Maturity Model Integration covers practices for planning, engineering and managing product development and maintenance. CMMI is the designated successor of the CMM.
Test Case for a Cell Phone
Subscribe the QA and Software Testing Newsletter Post Your Queries | QA and Testing - Table of Contents
SPONSORED LINKS
1. Check whether Battery is inserted into mobile properly 2. Check Switch on/Switch off of the Mobile
3. Insert the sim into the phone & Check
4. Add one user with name and phone number in Address book 5. Check the Incoming call
6. Check the outgoing call
7. send/receive messages for that mobile
8. Check all the numbers/Characters on the phone working fine by clicking on them..
9. Remove the user from phone book & Check removed properly with name and phone number 10. Check whether Network working fine..
11. If its GPRS enabled Check for the connectivity.
Test Case for a Traffic Signal
Subscribe the QA and Software Testing Newsletter Post Your Queries | QA and Testing - Table of Contents
SPONSORED LINKS
1. verify that signal has 3 coloured-red,green,yellow light 2. Power suppy is proper to it
3. Three lights work On n Off properly 4. Lights glow n dim in standard sequence
5. lights glow for specified time interval - red 1min, yello 10 sec n green 1 min 6. only one green light is On at a time on signal.
================================================================
======================
verify if the traffic lights are having three lights(green,yellow,red) verify that the lights turn on in a sequence
verify that lights turn on in a sequence based on time specified(greenlight-1min,yellowlight10sec,redlight 1 min)
verify that only one light glows at a time
verify if the speed of the Traffic light can be accelerated as time specified based on the traffic
verify if the traffic lights in some spots are sensor activated.
================================================================
======================
verify if the traffic lights are having three lights(green,yellow,red) verify that the lights turn on in a sequence
verify that lights turn on in a sequence based on time specified(greenlight-1min,yellowlight10sec,redlight 1 min)
verify that only one light glows at a time
verify if the speed of the Traffic light can be accelerated as time specified based on the traffic verify if the traffic lights in some spots are sensor activated.
Test Case for an Elevator
Subscribe the QA and Software Testing Newsletter Post Your Queries | QA and Testing - Table of Contents
SPONSORED LINKS
Some of the use cases would be:
1) Elevator is capable of moving up and down.
2) It is stopping at each floor.
3) It moves exactly to that floor when corresponding floor no is pressed.
4) It moves up when called from upward and down when called from downward.
5) It waits until 'close' button is pressed.
6) If anyon steps inbetween the door at the time of closing, door should open.
7) No break points exists
8) More usecases for the load that the elevator can carry (if required) ADDITIONAL:
1) When I push the call button, does it come to the floor and open the door after stopping?
2) Do the doors stay open for at least 5 seconds?
3) When closing, do the doors reverse if someone is standing in their way?
4) Does the elevator wait for someone to push a floor button before moving?
5) Does the elevator ignore the floor button of the current floor?
6) Does the floor button light up when pressed?
7) Does the Open Door button work when the elevator is moving?
8) Does the elevator travel in a smooth fashion?
9) Is there an up button on the top floor or a down button on the bottom floor?
What parameters to consider for Performance Testing?
generally we consider five parameters
what is conventional Testing? and what is unconventional testing?
Unconventional testing is a sort of testing done by the QA people, in which they test each and every documents right from the intial case of the 'SDLC'.
Where as conventional testing done by the test engineers on the application in the testing phase of the 'SDLC'.
What is the difference between User Controls and Master Pages Master pages and user controils are two different concepts.
Master pages are used to provide the consistent layout and common behaviour for multiple pages in your
applications.then u can add the Contenetplaceholder to add child pages custom contenet.
User Controls:Sometimes u need the functionality in ur web pages which is not possible using the Built-In Web server controls then user can create his own controls called user controls using asp.net builtin controls.User controlsn are those with .aspx extensions and u can share it in the application.
what is entry and exit criteria?
entry exit
unit test to check the modules white box testing level is done
integration exit of unit test WBT + BBT test
system test exit of integration 100% BBT test
UAT exit of system test may be WBT and compulsary BBT
Entry criteria is what has been agreed by relevant parties as to what needs to be completed before a particular phase of testing can begin. This can include fully documented release notes, completion of other test phases etc. Exit criteria is what needs to be completed before a test phase can finish. This can mean a certain percentage of test coverage, or based on there being only X number of critical bugs. Hope this helps further
What is the default identifier of structure in C? public