Manual_TestingPhases_SoftwareTesting

Based on the requirement provided by customers testers are going to validate the application.

There are two types of tests:-

1. Functional Testing
2. Non-Functional Testing

Functional Testing:

    Functional testing means, we are going to check the functionalities of the application as per the requirement given by the client.

Functional Testings are :

1. GUI (Graphical User Interface) Testing
2. Error Handling
3. Input domain Testing/Fuzz testing
4. Manipulation Testing/Functionality testing/Output testing
5. DB Testing (Database Testing)
6. Inter System Testing
7. Smoke Testing
8. Sanity Testing
9. Re-testing
10. Regression Testing

GUI Testing:

    Test the graphical item like Background colour, Fonts, Alignments, Size, Screens, ... every element.

Error Handling:

    Testing the error messages. (like invalid password, invalid username, ......)

Input domain Testing/Fuzz  Testing:

    Input domain testing uses a minimum number of inputs to check the output of a system. The purpose of this process is to prove that lies within the acceptable range.

Manipulation testing/Output testing/Functionality testing:-

    Based on 'test data' whatever we are going to input there will be certain output will be displayed.

Database Testing:-

    Checking the data that we are given, matches the database data.

(Databases: Sequal, Oracal, Mango, MySQL, No-SQL, ---)

Inter-System Testing:-

    In the inter-system testing, we going to check the connection between multiple screens' data flows.

Smoke Testing:-(done by the Developer)

    In this testing, they are going to check whether the new software builds do not disturb the core functionality of the project.

(Initial build verification testing)

Sanity Testing:-(done by the QA)

    During the sanity testing, they need to make sure that on a high level whatever newly deployed changes whether are working fine or not in order to continue in-depth testing.

Re-testing:-(done by the QA)

    Re-testing is done for the failed test cases. (we have tested already-but they got failed-the developers fixed them-Again testers re-testing them in order to make sure whether that working fine or not)

Regression Testing:- Testing already tested application. when new changes are happening in the application we will test the entire application again.

    When we do regression testing:

• When new functionality is added/deleted.
• Environment changes
• Bug fix