Manual_TestingPhases_SoftwareTesting2

 Non - Functional Testing:

1. Usability Testing
2. Compatibility Testing
3. Performance Testing
4. Security Testing
5. Multilanguity Testing
6. Compliance Testing
7. Parallel Testing

Usability Testing:

    How it is easily understandable by the user. testing the user-friendliness of the application.

Compatibility Testing:

    Check whether your software is capable of running on different Hardware, Operating Systems, Applications, Network Environments, Browsers etc.,

        Forward Compatability Testing: In this testing, we are going to verify whether the application was properly working or not in the future version of Hardware, OS, Browser etc.,

        Backward Compatability Testing: In this testing, we are going to verify whether the application was properly working or not in the older version of the Hardware, OS, Applications, Browsers etc.,

        (In real time we have never done this forward, backward compatibility testing. We are going to test only on updated software)

Performance Testing: (Tools: Load runner, JMeter,...)

    In order to find the speed of the process we do performance testing. Performance testing is done by the support team. 

    (As a QA we do network testing for that -> On the browser page -> press F12 (or SHIFT + F12)) -> Go to the 'Network' tab (here we can see response time))

    There are Four different types of performance testing

1. Load testing
2. Stress testing
3. Spike testing
4. Endurance testing

    Load testing:

        Whenever we are going to execute the application in the customer's expected environment with the customer's expected load to find the speed of the application this testing is called Load testing.

    Stress testing:

        This testing determines the software's robustness by testing beyond normal operating limits. That means testing the software more than the customer expected load. In order to identify the peek point of the application.

    Spike testing:

        To identify the server crashing point by increasing/decreasing the sudden load of the application.

    Endurance testing (Soak testing):

        The customer expected an environment with a customer-expected load but long duration. In order to identify the memory leakages, Security bridges.

Security testing/Penetration testing:

• Checking whether passwords are encrypted or not. (example: when we enter a password it will display Stars ****)
• Checking whether the URLs are Secure or not. (example: https://)
• Cookies are by default expire or not.
• Authorised users can be login into the application with valid credentials.
• After login into the web application copy the URL and paste it into another browser. check the web application opening without asking for credentials on other browsers.

Multilanguity:

    Testing the languages in the application like Hindi, Tamil, Telugu, Kannada, etc.,

        Localisation: The application displays only in the local language.

        Globalisation: Application displays in all languages in the Global (for example Facebook, Google)

Compliance Testing/Standard testing:

    We are going to check whether we are following standards or not.

    (This will be taken care of by the leads. Based on the requirement we are preparing test cases or not, whether the Developer is following standards for code or not, How many test cases we are writing for a day)

Parallel testing:

    In order to reduce the time, sometimes we do parallel execute the functions.