Manual Testing

What is Manual Testing?

                                   Manual Testing is part of software testing . it is manually execute the test  case in the no internal part of knowledge of code called as manual testing.

    Any website can't be munally 100% accuracy in test in the web application Product. but to check in web application in the require in the automation testing.

          For Example in the use in automation testing tool as the ...

          1) Selenium

          2)Jmeter

          3)Appium etc.

               it will be used in the automation tool in the Automate in Web application or Mobile testing.

Types Of Software Testing? 
         1) Black Box Testing

         2) white Box Testing

         3) Unit Testing

        4) System Testing

        5) Integration Testing

        6) Acceptance Testing

Difference Between Manual Testing vs Automation Testing:

Manual Testing:

    1) It is used for large number of QA used in test execution.

    2)Manual testing taking in long time and then cost of product is very high.

   3)Manual Testing is used in the ad-hoc and Mankey testing are used.

   4)Manual Testing take in long Time and Boring.

Automation Testing:

   1)It is use Tool and execute the test case.

   2)Automation testing save Time, Cast and manpower.

   3)Automaton Testing is using mostly Regression Testing.

   4) Automaton Testing to test in the boring part of and execute in the test cases.

Black Box Testing: 

        Black box testing is examines as Functionality of  an application based on the specifications.It is Called as specification based Testing.Independent Testing Team usually performs this type of testing during the software testing life cycle.

 Types Of Black Box Testing:

1)Incremental integration Testing :

                                            Incremental Testing is faster testing on the incomplete project.The goal of incremental testing is give on early feedback to the Developer.

2)End-to-end Testing :

                            End-to-End Testing is a type Software Testing that not only validates the software system under test but also checks its integration with external interfaces. Hence, the name "End-to-End". The purpose of End-to-End Testing is to exercise a complete production-like scenario.                 

4)Regression Testing :

                               Regression Testing is done to find out the defects that arise due to code changes made in existing code like functional enhancement or configuration changes.

3)Sanity Testing :

                          sanity testing in subset of regression Testing  and it performed when do not have enough time for doing testing .sanity Testing is the surface level Testing for Qa Enginner , Function, Commands, Avaliable in the Product are working fine.

4)Smoke Testing :

                  Smoke Testing is a build verification Testing that ensuring in complesive non-enhancive set of testing that is aim of main ensuring that is most important function work, the result is used to decide is build stable enough process is Further Testing. 

5)usability Testing: 

                                usability Testing easy to use , the ease  with which a user can learn to operate prepare input for and interrupts outputs of the software product?   

6)Install/uninstall Testing  :  

                        Testing of full, partial, or upgrade install/uninstall processes.                   

7)Recovery Testing  :

 Recovery testing is a type of non-functional testing technique performed in order to determine how quickly the system can recover after it has gone through system crash or hardware failure. Recovery testing is the forced failure of the software to verify if the recovery is successful.         

8)Security Testing:

                  Security Testing test the ability of system/software to prevent unauthorized access the resources and data.

9)Comparison Testing :

                    Comparison testing comprises of comparing the contents of files, databases, against actual results. They are capable of highlighting the differences between expected and actual results. Comparison test tools often have functions that allow specified sections of the files be ignored or masked out.                        

  White Box Testing:
                           white box testing is  the technique it examines the programe structure logic and design.The othe name is called as (Glass Box, clear box, Open box, Logic driven, Path Driven and structural testing.

Unit Testing: 
               An Unit testing technique using which individual modules are tested to determine if there are any issues by the developer himself. It is concerned with functional correctness of the standalone modules.

System Testing:               
                 System Testing (ST) is a black box testing technique performed to evaluate the complete system the system's compliance against specified requirements. In System testing, the functionalities of the system are tested from an end-to-end perspective.
 
  Types Of System Testing

              1) Functional Testing:

                      checking the Functinality of the system Application under Test(AUT)

              2) Inter-operability:

                      Inter-operability testing is a type of testing to check whether software can inter-operate   with other software component, software's or systems.

 
              3) Performance:

                             Performance testing, a non-functional testing technique performed to determine the system parameters in terms of responsiveness and stability under various workload. Performance testing measures the quality attributes of the system, such as scalability, reliability and resource usage.

                              

           Types of Performance Testing

                               1)Load Testing:    
                                                     Load Testing is type of performance testing to check system with constantly increasing the load on the system until the time load is reaches to its threshold value. Here Increasing load means increasing number of concurrent users, transactions & check the behavior of application under test.

                           2)Endurance Testing :
                                          Endurance testing is a non functional type of testing. Endurance testing involves testing a system with a expected amount of load over a long period of time to find the behavior of system.
                                      

                           3)Volume Testing:
                                   Volume testing is non-functional testing which refers to testing a software application with a large amount of data to be processed to check the efficiency of the application. The main goal of this testing is to monitor the performance of application under varying database volumes.        

                           4)Scalability Testing :
                                          Scalability Testing is type of non-functional tests and it is the testing of a software application for determine its capability to scale up in terms of any of its non-functional capability like the user load supported, the number of transactions, the data volume etc. The main aim if this testing is to understand at what peak the system prevent more scaling.                

                          5)Spike Testing:
                                          Spike testing is subset of Stress Testing. A spike test is carried out to validate the performance characteristics when the system under test subjected to workload models and load volumes that repeatedly increase beyond anticipated production operations for short periods of time.

                          6)Stress Testing :
                                       Stress Testing is performance testing type to check the stability of software when hardware resources are not sufficient like CPU, memory, disk space etc.

                         8)Reglatory  & Compliance:
                                   Regulatory compliance is an organization's adherence to laws, regulations, guidelines and specifications relevant to its business. Violations of regulatory compliance regulations often result in legal punishment, including federal fines.
                                         
                        9)Non Functional Testing:
                                                    checking Quality Attribute of the System (AUT)
                                               Quality Attribute:
                                                         Performance(Load, Stress, Spike, Endurance)
                    Usability:
                              Usability testing is a way to see how easy to use something is by testing it with real users. Users are asked to complete tasks, typically while they are being observed by a researcher, to see where they encounter problems and experience confusion.
                              
                    Recovery:
                              Recovery testing is a type of non-functional testing technique performed in order to determine how quickly the system can recover after it has gone through system crash or hardware failure. Recovery testing is the forced failure of the software to verify if the recovery is successful.
                               
                   compliance:
                          “Compliance testing” also know as Conformance testing is a nonfunctional testing technique which is done to validate, weather the system developed meets the organization's prescribed standards or not. There is a separate category of testing known as “Non Functional Testing”

                   Localization:
                            Localization testing checks the quality of a product's localization for a particular target culture/locale. This test is based on the results of globalization testing, which verifies the functional support for that particular culture/locale. ... Areas affected by localization, such as UI and content.
                  
                  Internationalization: 
                                        Software Internationalization is process of developing software products independent for cultural norms,language for other specific attributes of a market.

 Performance Testing Process:
                              a) Identify your testing environment
                              b) Identify the performance acceptance criteria
                              c) Plan & design performance tests
                              d) Configuring the test enviroment
                              e) Implement test design
                              f) Execute the tests
                              g) Analyze Result , Report, and Retest


Integration Testing: 
             The purpose of integration testing is to verify the functional, performance, and reliability between the modules that are integrated.

Acceptance Testing:
                             Acceptance testing, a testing technique performed to determine whether or not the software system has met the requirement specifications. The main purpose of this test is to evaluate the system's compliance with the business requirements and verify if it is has met the required criteria for delivery to end users.
      Types Of Acceptance Testing 
          
              1) User acceptance Testing:
                           User acceptance testing, a testing methodology where the clients/end users involved in testing the product to validate the product against their requirements.
              2)Business acceptance Testing:
                                BAT (Business Acceptance Testing) is primarily focused on assessing the business requirement of an organization and deals with strategy. It is based on approach, dynamics, culture, information technology, statutory requirements, operational framework and customers.
              3)Alpha Testing:
                        Alpha Testing is performed by the in house developers  and software quality assurance people.
                             
              4)Beta Testing:
                               Beta Testing of a re-release of a software product by customer.