QA Test level and Testing Types

QA Test level and Testing Types

1. Requirement

   • A condition or capability needed by a user to solve a problem or achieve and objective.
   • Functional Requirement
     • An initial definition of the proposed system, which documents, goals, user or programmatic requirements, and the proposed design methodology, eg, centralized or distributed.
   • Non Functional Requeriment
     • A requirement that does not relate to functionality, but attributes such as reliability, usability, maintainaibility, and portability.

2. Testing levels

   • Testing
     • It is a process of evaluating a system or components of the system manually or automatically to verify differences between current and expected results.
   • Identify missing areas and prevent overlap and repetition between the development life cycle phases.
     • Unit
       • It is done by the developers to make sure that their code is working fine and meet the user specifications.
     • Integration
       • Integration testing is done when two modules/components are integrated, in order to test the behavior and functionality of both the modules after integration.
     • System
       • In system testing the testers test the compatibility of the application with the system, but also, the behavior of whole system/product is tested as defined by the scope of the development project or product.
     • Usser Acceptance
       • Acceptance testing are done to ensure that the requirements of the specification are met.
     • Alpha
       • Alpha testing is done at the developers site. It is done at the end of the development process.
     • Beta
       • Beta testing is done at the customers site. It is executed just before the launch of the product. It is also known as field testing.
   • Software Testing
     • Software testing is a process of executing a program or application with the intent of finding the software bugs.
     • Software Testing Type
       • Software Testing Type is a classification of different testing activities into categories, each having, a defined test objective, test strategy, and test deliverables.
       • Types of Software Testing
         • Black Box Testing
           • The main purpose of Black Box Testing is to validate that the application works as the user will be operating it and in the environments of their systems.
           • Levels
             • Integration Testing
             • System Testing
             • Acceptance Testing
         • White Box Testing
           • It is a software testing method in which the internal structure/design/ implementation of the item being tested is known to the tester.
           • Main purpose
             • Internal security holes
             • Broken or poorly structured paths in the coding processes
             • The flow of specific inputs through the code

3. Funtional Testing

   • It refers to activities that verify a specific action or function of the code. Functional test tends to answer the questions like “can the user do this” or “does this particular feature work”.
   • End to end testing
     • End-to-end testing is a methodology used to test whether the flow of an application is performing as designed from start to finish.
   • Regression Testing
     • Corrective Regression testing
       • This type of testing is used when there are no changes introduced in the product’s specification.
     • Progressive Regression Testing
       • This type of regression testing works effectively when there are certain changes done in the program specifications as well as new test cases are designed.
     • Selective Regression testing
       • It is done to analyze the impact of new code added to the already existing code of the software.
     • Complete Regression testing
       • Complete regression testing is the best to be used in case there are multiple changes that have been done to the already existing code.
     • Types of Regression Bugs
       • Local : Modification or changes in the code generate new bugs
       • Unmasked : Modification or code changes shows existing errors
       • Remote : Modification or changes in the code negatively affect other parts of the system
   • Smoke Testing
     • Smoke testing is a type of software testing which ensures that the main functionalities of the application are working fine.
   • Sanity Testing
     • Sanity Testing purpose is verify than fixing process doesn’t affect the other functionalities which were working properly.

4. Non Functional Testing

   • In non-functional testing the quality characteristics of the component or system is tested.
   • Performance
     • Performance testing is oriented to determine a system’s performance, validate the quality attributes (such reliability, stability) of the system, expose the bottle necks, and measure the peak of loads.
     • Types
       • Load Test
         • It tests an application under normal loads to determine the response times for various critical transactions or business processes to determine whether it meets a requirement.
       • Stress Test
         • This evaluates a system at the specified limitation of resources to determine the load under which it fails and how.
       • System performance
         • The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate.
       • Stability Test
         • Tests a system at different levels of loads for prolonged periods of time.
       • Time Response Test
         • The basic performance test and one of most concern by end-user
       • Data Volume Test
         • It is designed specifically for applications that access huge stores of data.
   • Security
     • Security testing is a type of software testing that’s done to check whether the application or the product is secured or not.
     • Injection
     • Broken Authentication
     • Sensitive Data Exposure
     • XML External Entities (XXE)
     • Broken Access Control
     • Security Misconfiguration
     • Cross-Site Scripting (XSS)
     • Insecure Deserialization
     • Using Components with Known Vulnerabilities
     • Insufficient Logging & Monitoring
   • Accessibility
     • accessibility testing helps you understand how people with disabilities use your product, which then allows you to help produce quality software that is accessible to everyone.
   • Usability
     • In Usability testing the testers tests the ease with which the user interfaces can be used.
   • Portability
     • It refers to the process of testing the ease with which a computer software component or application can be moved from one environment to another.
   • Reliability
     • Reliability Testing is about exercising an application so that failures are discovered and removed before the system is deployed.