Author: Neftaly Malatjie

  • 114066 LG 1.21 Identify Testing Type

    1. A Testing Type is a standard test procedure that gives an expected test outcome.

      Each testing type is formulated to identify a specific type of product bugs. But, all Testing Types are aimed at achieving one common goal “Early detection of all the defects before releasing the product to the customer”

      The commonly used testing types are described as following figure;

    3. There are tons of Testing Types for testing software product. Your team cannot have enough efforts to handle all kind of testing. As Test Manager, you must set priority of the Testing Types

      • Which Testing Types should be focused for web application testing?
      • Which Testing Types should be ignored for saving cost?

  • 114066 LG 1.20 Problem Scenario

    1. The customer wants you to test his API. But the project budget does not permit to do so. In such a case what will you do?

      Well, in such case you need to convince the customer that API testing is extra work and will consume significant resources. Give him data supporting your facts. Tell him if API testing is included in-scope the budget will increase by XYZ amount.

      The customer agrees and accordingly the new scopes, out of scope items are

      • In-scope items: Functional Testing, API Testing

      Out of scope items: Database testing, hardware & any other external

  • 114066 LG 1.19 Define Scope of Testing

    1. Before the start of any test activity, scope of the testing should be known. You must think hard about it.

      • The components of the system to be tested (hardware, software, middleware, etc.) are defined as “in scope“
      • The components of the system that will not be tested also need to be clearly defined as being “out of scope.”

      Defining the scope of your testing project is very important for all stakeholders. A precise scope helps you

      • Give everyone a confidence & accurate information of the testing you  are doing
      • All project members will have a clear understanding about what is tested and what is not

      How do you determine scope your project?

      To determine scope, you must –

      • Precise customer requirement
      • Project Budget
      • Product Specification
      • Skills & talent of your test team

      Now should clearly define the “in scope” and “out of scope” of the testing.

      • As the software requirement specs, the project Guru99 Bank only focus on testing all the functions and external interface of website Guru99 Bank (in scope testing)
      • Non-functional testing such as stress, performance or logical database currently will not be tested. (out of scope)

  • 114066 LG 1.34 INTEGRATION TESTING PROCEDURE

      • The goal of integration testing is to ensure that all interacting subsystems in a system interface correctly with one another to produce the desired results.  Furthermore, in trying to attain this goal, integration tests will ensure that the introduction of one or more subsystems into the system does not have an adverse effect on existing functionality.

        An integration test covers the testing of interface points between subsystems.  Integration testing is performed once unit testing has been completed for all units contained in the subsystems being tested.  Integration Testing Procedures consist of:

        •  Creating and integration test plan
        •  Creating test data
        •  Conducting tests according to the integration test plan
        •  Reporting and reviewing the results of the test

        During this phase, the interaction between subsystems is tested.  This includes interfaces through Inter Process Communications (IPC) and files.  This phase is performed by an independent test team.  This team prepares and executes integration tests, generates problem reports and is responsible for passing the integrated system on to the System Test Team for system testing.  The Integration Test team then enters a support mode in which it will test problem reports generated by the System Test team before forwarding code fixes to the System Testing environment.

        This phase is sometimes combined with the system test phase as per the client’s

  • 114066 LG 1.33 Conduct Unit Test

      • Unit testing is performed according to the following procedures:

        • Unit tests will be run according to the Unit test Plan created by the developer
          If any of the actual results do not agree with the expected results, the developer fixes the code and re-runs the test. There is a possibility that the Unit Test Plan will need to be updated if it is determined that the Unit Test Plan is not correct or no longer up-to-date
        • Once all test cases have been successfully completed the developer signs the top page of the test plan, completes a promotion request form and passes the package to the developers team leader
        • The team leader verifies that the unit test has been performed and the team leader (or developer) passes the promotion request to Configuration Management