Introduction to Software Testing-Part two

I am continuing my previous post “Introduction to software testing-Part one” .In my previous post I shared the basic process steps of software testing. Now in this post I am going to share high level classification of testing and some basic terms used in testing. In this post I have used some mind maps.I have used mind maps first time and credit goes to "Ajay" who suggested me to use mind maps.It was good experience to use and learn mind maps.

High Level Classification of Testing:

High Level Classification of  software testing

Basic terms used in software testing:

Test Scenarios:   Test scenarios provides  high-level description of the functionalities we need to test for. For example: There is a home page of website and on Home page Login functionality is present so here test scenarios for Login functionality would be:

Example of Test Scenarios

Test Cases: Test cases are the conditions which we test for any particular scenarios and test cases provides more details of functionalities. For Example: For the scenario “Active user tries to login” following could be the test cases:

Example of Test cases

Bug/Defect: This is most interesting thing for testers. This is the output of testing effort . Any behaviour  of the system which is not according to the requirement and any behaviour which negatively impacts the system is a bug/defect. Bug can be related to functional behaviour, UI behaviour, Usability behaviour ,Performance behaviour and  Security  behaviour of the application.

Points to remember for raising bugs:

Bug-Points to remember

Metrics:  During the testing process we collect some kind of information data like No. of defects by severity or no. of defects by phase, Defect Injection rate, Defect removal Efficiency etc. which is called metrics. A good set of metrics provides the direction, it tells us testing status at any given point of time .

Smoke Testing:  Smoke testing usually we perform when any new build of application is available for testing. We do smoke testing to verify whether system is quite stable for the testing  or not. If system is stable then only we proceed with the further testing

Regression Testing:   We do regression testing to verify that new modifications/enhancements does not negatively impact the existing behaviour of the system (which should not be changed as part of new modification/enhancement).

Retesting: During testing if we face any issue in any test case then we raise bug  and that test case status will be fail. Now when the fix of that bug will be available in that case we have to verify that bug as well as we have to test that test case which was failed due to this bug. Testing of same test case again when the associated bug is resolved  is called retesting.

Exploratory Testing:  In Exploratory testing we learn as well as test the application at the same time. More details of exploratory testing we can get here:

http://www.satisfice.com/articles/what_is_et.shtml

http://www.satisfice.com/articles/et-article.pdf