Common Testing Concepts Cheat Sheet by narbit

1. Sanity Testing is type of testing that QA perform after receiving the software build, sanity testing is performed to ensure that the code changes introduced are working as expected .This testing is a checkpoint to determine if testing for the build can proceed or not.

3. Unit Testing is a type of software testing where individual units or components of a software are tested. The purpose is to validate that each unit of the software code performs as expected.

5. Functional Testing is a type of software testing that validates the software system against the functional requir­eme­nts­/sp­eci­fic­ations. The purpose of Functional tests is to test each function of the software applic­ation, by providing approp­riate input, verifying the output against the Functional requir­ements.

7.System Testing is testing conducted on a complete integrated system to evaluate the system's compliance with its specified requir­ements.

9. Perfor­mance Testing is is a testing measure that evaluates the speed, respon­siv­eness and stability of a computer, network, software program or device under a workload.

11. Usability Testing is the practice of testing how easy a design is to use with a group of repres­ent­ative users.

1. STP is the Software Test Plan document describes plans for qualif­ication testing of Computer Software Config­uration Items (CSCIs) and software systems. It describes the software test enviro­nment to be used for the testing, identifies the tests to be performed, and provides schedules for test activi­ties.

3. STR is the Software Test Report is a record of the qualif­ication testing performed on a Computer Software Config­uration Item (CSCI), a software system or subsystem, or other softwa­re-­related item.

5. RTM is a requir­ements tracea­bility matrix document that demons­trates the relati­onship between requir­ements and other artifacts. It's used to prove that requir­ements have been fulfilled. And it typically documents requir­ements, tests, test results, and issues.

Agile- the develo­pment model of software develo­pment is a conceptual framework for software engine­ering that promotes develo­pment iterations throughout the life-cycle of the project. The Agile approach meaning as the name refers implies something to do very quickly.

1.Saving time and money. 2.Focus more on the applic­ation rather than docume­nting things. 3.Daily meetings and discus­sions for the project following an Agile model can help to determine the issues well in advance and work on them accord­ingly. 4.Requ­ire­ments changing even in the late stage of develo­pment .5.The end result is high-q­uality software in the least possible time duration and satisfied customers.

1.The project can easily get taken off track if the customer repres­ent­ative is not clear what final outcome that they want. 2.There is a lack of emphasis on necessary designing and docume­nta­tion. 3. User involv­ement is often a potential problem especially in big and complex projec­ts.4. Agile processes are really only applicable to products where reliab­ility is not very critical.

V-Model This is the most familiar model in the develo­pment process. The model has the form of a “V”. The main idea in the V-Model is that develo­pment tasks and testing tasks are corres­ponding activities of equal import­ance, which is symbolised by the two sides of the “V”

1.Due to the fact that in the V-Model defects are being repaired a short time after they have been detected, it is cheaper to fix them. 2.The model has a reputation for a very good base for the partit­ioning of testing. All the partic­ipants in the develo­pment of a system have a respon­sib­ility for quality assurance and testing. 3.Testing activities like requir­ements, test designing happen well before coding. This fact saves a lot of time and also helps in developing a very good unders­tanding of the project at the initial stage. 4.The objectives of testing are changing, and specific for each test level.

1.The V-Model is very rigid and the least flexible, which means that if one of the requir­ements is changing, the tester should update the test docume­ntation as a whole. 2. This model applicable mostly to big companies because the model needs a lot of resources. 3.The amount and the intensity of the test levels should be tailored according to the specific needs of the project.