• RSS
  • Facebook
  • Twitter

One Center for all the Testing Need. OneTestingCenter is for all, for all QA, for all Automation. Automation is easy, fun and enriching experience. Happy Learning and Happy Testing!

  • Access to All QA

    At OneTestingCenter, you find lots of books,articles,blogs and detailed guides. Everyone has access to QA. Happy Learning, Happy Testing.

  • Global Trainings

    All the QA/Auotmation trainings are available at OneTestingCenter. QA, Automation, QTP/UFT, Selenium, LoadRunner, QC/ALM, Appium...

  • Automation Learning Fun

    Technology is always evolving. Automation is always challenging. To be frank, Automation is fun, enthusiastic and enrching experience.




    Smoke Testing:
    Smoke Testing is the process of testing the application at starting state (at initial stage) to check
    o   If the core requirements are working fine
    o   If the build can be accepted for major testing
    Functional Testing:
    Functional Testing is the process of testing individual modules (each and every module) of the application to check if the application is behaving as per the requirements.
    Integration Testing:
    Integration Testing is the process of testing combined modules (integrated module) of the application to check if the application is behaving as per the requirements.
    Integration Testing could be done in two ways:
    o   Integration between Application modules
    §  Navigations between Modules
    o   Data Flows between Modules
    §  Integrity between modules
    o   Integration between Application Software
    §  Connections and Integrations between Apps
    System Testing:
    System Testing is the process of testing complete application to check if the application is behaving as per the requirements.
    o   End to End Testing
    o   Start to End Testing
    o   User Scenarios Testing
    Regression Testing:
    Regression Testing is the process of testing application to check if the existing functionality is not affected by bug fixes / code changes or new enhancements of the application.
    o   Build Specific Test
    o   Way of System Testing
    Retesting: 
    Retesting is the process of the testing application with same sets of test cases / test scenarios executing for multiple times, with multiple sets of test data.
    o   This is called Data Parameterization Tests
    o   Same tests can be repeated for multi times with multi sets of test data.
    Bug Verification:
    Bug verification is the process of testing the fixes / issues (that are reported by QA and fixed by Dev) to confirm if the issues are fixed and are working well without impacting the existing functionality of the application.
    o   Build Oriented Testing.
    o   Continued until end of the testing process on all builds
    Automation Testing:
    Automation Testing is the process of utilizing a tool or software to design, to control, to execute manual tests .
    o   Smoke Testing
    o   Functional Testing
    o   Regression Testing
    Compatibility Testing: 
    Compatibility Testing is the process of testing application to check how well the application is compatible with respect to the different browsers / different OS / different hard ware.
    ·         Browsers : IE , Mozilla, Chrome
    o   Versions : IE 6, IE 7, IE 8, IE 9
    o   OS : XP / Vista / Windows 7
    Installation Testing: 
    Installation Testing is performed to ensure that all the Installed features and options of the software are functioning properly. Its main objective is to verify that all necessary components of the application are actually installed or not without missing out any component.

    UAT > User Acceptance Testing:
    o   UAT is customer verification testing.
    o   It can be done in two ways
    ·         Alpha Testing (α)
    ·         Beta Testing (β)
    o   Alpha Testing is often performed by potential users / customers or an independent test team at the developers' site.
    o   It is usually done when the development of the software product is nearing completion; minor design changes may still be made as a result of Alpha testing. 
    o   The second stage coming after alpha testing is known as "Beta Testing".
    o   Versions of the software, known as beta versions, are released to a limited audience outside of the programming team so that further evaluation by the users can reveal more faults or bugs in the product.
    o   Sometimes, beta versions are made available to the open public to increase the feedback field to a maximum number of future users.
    o   Usually it is done at customer places or customer like places (end users)

    Reactions:

    Testing Types & Definitions




    Smoke Testing:
    Smoke Testing is the process of testing the application at starting state (at initial stage) to check
    o   If the core requirements are working fine
    o   If the build can be accepted for major testing
    Functional Testing:
    Functional Testing is the process of testing individual modules (each and every module) of the application to check if the application is behaving as per the requirements.
    Integration Testing:
    Integration Testing is the process of testing combined modules (integrated module) of the application to check if the application is behaving as per the requirements.
    Integration Testing could be done in two ways:
    o   Integration between Application modules
    §  Navigations between Modules
    o   Data Flows between Modules
    §  Integrity between modules
    o   Integration between Application Software
    §  Connections and Integrations between Apps
    System Testing:
    System Testing is the process of testing complete application to check if the application is behaving as per the requirements.
    o   End to End Testing
    o   Start to End Testing
    o   User Scenarios Testing
    Regression Testing:
    Regression Testing is the process of testing application to check if the existing functionality is not affected by bug fixes / code changes or new enhancements of the application.
    o   Build Specific Test
    o   Way of System Testing
    Retesting: 
    Retesting is the process of the testing application with same sets of test cases / test scenarios executing for multiple times, with multiple sets of test data.
    o   This is called Data Parameterization Tests
    o   Same tests can be repeated for multi times with multi sets of test data.
    Bug Verification:
    Bug verification is the process of testing the fixes / issues (that are reported by QA and fixed by Dev) to confirm if the issues are fixed and are working well without impacting the existing functionality of the application.
    o   Build Oriented Testing.
    o   Continued until end of the testing process on all builds
    Automation Testing:
    Automation Testing is the process of utilizing a tool or software to design, to control, to execute manual tests .
    o   Smoke Testing
    o   Functional Testing
    o   Regression Testing
    Compatibility Testing: 
    Compatibility Testing is the process of testing application to check how well the application is compatible with respect to the different browsers / different OS / different hard ware.
    ·         Browsers : IE , Mozilla, Chrome
    o   Versions : IE 6, IE 7, IE 8, IE 9
    o   OS : XP / Vista / Windows 7
    Installation Testing: 
    Installation Testing is performed to ensure that all the Installed features and options of the software are functioning properly. Its main objective is to verify that all necessary components of the application are actually installed or not without missing out any component.

    UAT > User Acceptance Testing:
    o   UAT is customer verification testing.
    o   It can be done in two ways
    ·         Alpha Testing (α)
    ·         Beta Testing (β)
    o   Alpha Testing is often performed by potential users / customers or an independent test team at the developers' site.
    o   It is usually done when the development of the software product is nearing completion; minor design changes may still be made as a result of Alpha testing. 
    o   The second stage coming after alpha testing is known as "Beta Testing".
    o   Versions of the software, known as beta versions, are released to a limited audience outside of the programming team so that further evaluation by the users can reveal more faults or bugs in the product.
    o   Sometimes, beta versions are made available to the open public to increase the feedback field to a maximum number of future users.
    o   Usually it is done at customer places or customer like places (end users)