Test scenario is any functionality of the application under test, that can be tested. It is also called test condition or test possibility Check login functionality Check new order Check open order Test data : Test data is input given to the software program. It represents data the affects or affected by the execution of […]
Test plan : A test plan is derived from software requirement specification (SRS) describing in detail the scope of the testing and the different activities performed in testing. Test plan is a project level. It describes the whole testing activities in detail the techniques used, schedule, resources etc.. Test plan usually exits individually Test strategy […]
Functional and non functional need which implemented in the system. Each requirement expressed as a statement. Requirement types : Business requirement Architectural and design requirement System requirement and integration requirement Other source of requirements : Knowledge transfer Business analyst, product manager, developers, project manger or client Prior system versions Older requirements Part bug reports Install […]
Requirement analysis ( BRS/ FRS Review) Test strategy and test plan Creating test specification Test scenario preparation Test data preparation Peer review Requirement traceability matrix Introduction to test management and bug tracking tool Build deployment Conducting build acceptance testing ( Sanity) Conducting system testing Formal testing Adhoc testing Exploratory testing Retesting Regression testing End to […]
Any mismatched functionality found in a application is called as defect/Bug/Issue. During test execution test engineers are reporting mismatches as defects to developers through templates or using tools. Defect reporting tools : Clear quest Dev track Jira Quality center Bug zilla Defect report contents : Defect is – Unique identification for the number for the […]
Use case Use case describes the requirement Use case contains three items which is Actor Action Outcome Test scenario Possible area to be tested (what to test) Test case How to test Describes test steps, expected result vs actual result Use case Describes the functional requirement, prepared by business analyst Test case Describes the test […]
Test design technique helps you design better cases. Since exhaustive testing is not possible , testing techniques helps to reduce the number of test cases to be executed while increasing test coverage. They help to identify test conditions that are otherwise difficult to recognize. Boundary value analysis Equivalent class partitioning Decision table based testing State […]
End to end testing is testing the overall functionality of the system including the data integration among all the modules is called end to end testing. End to end test : Login 2. Add customer 3. Delete customer 4. Edit customer 5. Logout
Smoke testing Smoke testing is performed to certain that the critical functionalities of the program is working fine. The objective of this testing is to verify the stability of the system in order to proceed with more rigorous testing. This testing is performed by the developers or testers. Smoke testing is usually documented or scripted […]
Adhoc testing is informal testing type with an aim to break the system. It doesn’t require any test case design technique to create test cases. This testing primarily performed if the knowledge of the testers in the system under test is very high. It doesn’t create testcase design altogether. It is a unplanned activity. Randomly […]