Scribd
Upload
23 views2 pages

Testing

Testing

Uploaded by

Nathan Ombui
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
23 views2 pages

Testing

Testing

Uploaded by

Nathan Ombui
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Testing

Process of verifying and validating a software, website or application.


Ensuring product is bug free.
Ensuring the product meets business requirements
Ensuring product meets technical requirements
Ensuring the product efficiently handles all use cases

Objectives of Testing
 Bug Detection
 Bug Prevention
 Assure quality of software
 Increase Customer satisfaction
 Increase Security, Usability, Performance
 Reduce Costs
 Improvement in process

Principles of Testing
 Testing shoes presence of defects
 Exhaustive testing is not possible
 Early testing
 Defect clustering
 Pesticide paradox
 Testing is context dependent
 Absence of errors fallacy

Common Testing Terms


Error: A mistake, misconception, or misunderstanding made by humans that leads to discrepancy
Defect: The variation between the actual results and expected results.
Bug/Ticket/Incident: Synonyms of the Word “Defect” used interchangeably in companies. For example
some companies call it a “Bug” if its detected by real users.
Failure: Anything that causes the software to fail to perform its required function.
Debugging: The process of finding, analyzing and removing the causes of failures in software.
Verification: The process of evaluating work-products (not the final product) to determine whether they
meet the specified requirements. “Are we building the product right?”
Validation: The process of evaluating software during or at end of development process to determining
whether it satisfies specified business requirements. “Are we building the right product?”
Black Box Testing: Testing without any reference to internal structure of components/system
White Box Testing: Testing based on an analysis of internal structure of a component/system.
Severity: Indicates the degree of impact the defect has on functionality of component or system (Tester’s
Evaluation)
Priority: Indicates how quickly the bug should be fixed. (Business’s evaluation)
Agile Testing: Testing practice for a project using agile methodologies, such as emphasizing the test-first
design (TDD).
Continuous Testing: Testing practice that involves the process of testing early on, testing more often,
testing everywhere, and automating.
Test Scenario
Any Functionality that can be tested. Also called Test Possibility or Test Condition. As a tester, you put
yourself in the end user’s shoes and figure out the real-world scenarios and use cases of the Application
Under Test
How To Create Test Scenarios
1. Study the Requirements Document – Business Requirement Specification (BRS), Software
Requirement Specification (SRS), Functional Requirement Specification (FRS) pertaining to the
system Under Test (SUT).
2. Isolate every requirement, and identify what possible user actions need to be tested for it.
3. Enumerate test scenarios that cover every possible feature of the software. Ensure that these
scenarios cover every user flow and business flow involved in the operation of the website or
app.
4. Create Traceability Matrix to ensure that every requirement is mapped to a test scenario.
5. Get the scenarios reviewed by a supervisor, and then push them to be reviewed by other
stakeholders involved in the project

You might also like