Testing

Types of Testing:

1. Unit Testing: The process of testing a particular compiled program independently as a standalone component program.

2. Incremental testing is partial testing of incomplete product. The goal of incremental testing is to provide an early feedback to software developers. 

3. System testing is a form of blackbox testing. The purpose of system testing is to validate in applications accuracy and completeness in performing the functions as design. 

4. Integration testing. Testing two or more modules or functions together with the intent of finding interface defects between the module functions. 

5. System integration testing. Testing of software components that have been distributed across multiple platforms.

6. Functional testing. Verifying that a module functions as stated in the specification and establishing confidence that a program does what it is supposed to do.

7. UI Testing

8. UAT Testing: User Acceptance Testing

9. Accessibility

10. Ad-hoc

11. Regression: Test integrated functionalities. 

12. Sanity

13. Stress

14. Blackbox

15. Whitebox

16. End-to-end

17. Smoke: Quick random test for the major functionalities. 

Test plan:

Objectives: The aim of the testing

In Scope: modules to be implemented and tested

Out of scope: modules not to be tested.

Assumptions

Entry/Exit Criteria:

Entry:

    Approval of this test plan by the management

    All database, development, and business teams should be notified about system test dates.

Exit:

    Test cases for mentioned modules should be created

    All the modules should be tested

    Test evidence will be provided to the management

    All the mentioned deliverables should be completed and signed off

Environment:

    System Test Platform

    Access to requirements documents links to SharePoint

    Access to test management tool

Risks

Key Dates and Deliverables

Scripts and Files

Roles and Responsibilities

Closure

The test plan describes what to test.

A test case describes how to perform a particular test.

Test Case:

1.1: Signin module will have a username and password field. User should be able to enter their credentials on those fields and click on Login for accessing their accounts.

Requirement Reference	Test Case#	Pre-Condition	Objective	Test Step#	Detailed Test Step	Expected Results	Execution Result
1.1	1	User should be given the system test environment of the homes.com platform	To test the login functionality of homes.com with invalid credentials	1	Launch the Firefox browser and navigate to www.homes.com	The homes.com home page should appear succesfully	Pass

Life Cycle models:

1. Waterfall

2. Prototyping

3. Spiral

Software Testing Lifecycles:

1. Planning

2. Analysis

3. Design

4. Construction

5. Testing Cycles

6. Final Testing & Implementation

7. Post Implementation

Levels of Testing

1. Unit Testing: To verify a single program or a section of a single program.

2. Integration Testing: To verify interaction between system components, pre-requisite, unit testing completed on all components that compose a system.

3. System Testing: To verify and validate behaviours of the entire system against the original system objectives.

Testing Terms:

1. Bug

2. Error:

• User Interface Errors
• Error Handling
• Boundary related errors
• Calculation errors
• Initial and Later states
• Control flow errors
• Errors in Handling or Interpreting Data
• Race Conditions
• Load Conditions
• Hardware
• Source, Version and ID Control
• Testing Errors

3. Defect

4. Failure

5. Quality Assurance

6. Quality Control

7. Verification

8. Validation