Best software testing course

  • View

  • Download

Embed Size (px)




    B E S T O N L I N E C O U R S E S C O U P O N . C O M


    About software testing Quality Testing Quality Assurance Quality Control ISO Standards Types of TestingMethods Levels Documentation Estimation Techniques


    Software testing is the primary process of verifying and

    validating the software program or the product. It is also an

    investigation which is conducted to offer stakeholders with

    required information about service test or the product quality. It

    has a view that the software allows you to check out the

    software implementation by understanding and appreciate it.

    On the other side, usually, the test techniques majorly include

    the program to execute and find the errors to check out

    whether the product is ready to use or not.


    It includes activities that ensure the identification

    of bugs/error/defects in a software.

    Focuses on actual testing.

    Product-oriented activities.

    It is a preventive process.

    Testing is the subset of Quality Control.


    QA includes activities that ensure the implementation of

    processes, procedures and standards in context to verification

    of developed software and intended requirements.

    Focuses on processes and procedures rather than conducting

    actual testing on the system.

    Process-oriented activities.

    Preventive activities.

    It is a subset of Software Test Life Cycle (STLC).


    It includes activities that ensure the verification of a

    developed software with respect to documented (or not

    in some cases) requirements.

    Focuses on actual testing by executing the software

    with an aim to identify bug/defect through

    implementation of procedures and process.

    Product-oriented activities.

    It is a corrective process.

    QC can be considered as the subset of Quality


  • ISO STANDARDS Many organizations around the globe develop and implement different standards to improve the quality needs of their software. This chapter briefly describes some of the widely used standards related to Quality Assurance and Testing.

    ISO/IEC 9126 ISO/IEC 9241-11 ISO/IEC 25000:2005 ISO/IEC 12119

  • ISO/IEC 9126 This standard deals with the following aspects to determine the quality of a software application:Quality model,External metrics,Internal metrics,Quality in use metrics

    quality attributes for any software such as: Functionality,Reliability,Usability,Efficiency, Maintainability,Portability

  • ISO/IEC 9241-11 Part 11 of this standard deals with the extent to which a product can be used by specified users to achieve specified goals with Effectiveness, Efficiency and Satisfaction in a specified context of use.

    This standard proposed a framework that

    describes the usability components and the

    relationship between them.

    the usability is considered in terms of user

    performance and satisfaction.

  • ISO/IEC 25000:2005

    ISO/IEC 25000:2005 is commonly known as the standard that provides the guidelines for Software Quality Requirements and Evaluation (SQuaRE). ISO-25000 replaces the two old ISO standards, i.e. ISO-9126 and ISO-14598.

  • ISO/IEC 12119 This standard deals with software packages delivered to the client. It does not focus or deal with the clients production process.

    The main contents are related to the following items:

    Set of requirements for software packages. Instructions for testing a delivered software package against the specified requirements.


    The testing has the different types of testing which are

    mainly used to test software.They are

    Manual Testing

    Automation Testing


    Manual testing includes the testing of software

    manually which means without using any of the

    automated script or the tool. In this manual testing

    type, the tester will take over the testing to check out

    whether there is an identity of any unexpected errors

    or behavior occurs.


    Test Automation, whereas on the other side tester

    which will help to write the scripts and it uses the

    other software which is use to test the product. Thus

    the process involves the manual process of its

    automation. It also helps to re-run the performance to

    look for scenarios which are performed quickly,

    manually and the repeatedly.

  • METHODS The software methods are used for the testing software purposes.

    There are different methods that can be used for software testing.:

    Black-Box TestingWhite-Box Testing Grey-Box Testing


    The internal workings of an application need not be known.

    Also known as closed-box testing, data-driven testing, or functional testing.Performed by end-users and also by testers and developers. Not suited for algorithm testing. Testing is based on external expectations - Internal behavior of the application is unknown. This can only be done by trial-and-error method.


    Tester has full knowledge of the internal workings of the application.

    Also known as clear-box testing, structural testing, or code-based testing. Normally done by testers and developers. The most exhaustive and time-consuming type of testing. Suited for algorithm testing. Data domains and internal boundaries can be better tested.


    The tester has limited knowledge of the internal workings of the application.

    Also known as translucent testing, as the tester has limited knowledge of the insides of the application. Performed by end-users and also by testers and developers. Partly time-consuming and exhaustive. Not suited for algorithm testing. Data domains and internal boundaries can be tested, if known.


    The online software testing course has two different level testing. The level of testing which mainly includes the different method that is used during the software testing. The two main levels are,

    Functional Testing Non-functional Testing


    Functional Testing is the type of black box

    testing which is based on the software

    specifications to be tested.

    Thus the application is tested by the results and

    the inputs according to the functionality.

    Functional testing of the software is placed on

    the integrated system to correct the systems

    observance with requirements.


    Non-Functional Testing is based on testing the

    application from its attributes.specifications to

    be tested.

    It mainly involves the software testing from the

    given requirements as well.


    The software Testing documentation is an IEEE standard specifies the set of documents for the primary use in different defined stages of system testing and software testing. There are different types of documents are

    Test Plan Test Scenario Test Case Traceability Matrix


    A Test Plan includes the following:

    Introduction to the Test Plan document Assumptions while testing the application List of test cases included in testing the application List of features to be tested What sort of approach to use while testing the software List of deliverables that need to be tested The resources allocated for testing the application Any risks involved during the testing process A schedule of tasks and milestones to be achieved


    It is a one line statement that notifies what

    area in the application will be tested.

    Test scenarios are used to ensure that all

    process flows are tested from end to end.

    A particular area of an application can have as

    little as one test scenario to a few hundred

    scenarios depending on the magnitude and

    complexity of the application.

  • TEST CASE Test cases involve a set of steps, conditions, and inputs that can be used while performing testing tasks. components are always available and included in every test case:

    Test case ID Product module Product version Revision history Purpose Assumptions Pre-conditions Steps Expected outcome Actual outcome Post-conditions


    Traceability Matrix (also known as Requirement Traceability Matrix - RTM) is atable that is used to trace the requirements during the Software Development Life Cycle. The main goals for this matrix are:

    Make sure the software is developed as per

    the mentioned requirements.

    Helps in finding the root cause of any bug.

    Helps in tracing the developed documents

    during different phases of SDLC.


    The testing has the estimation which is mainly required

    one of the important things in SDLC.

    Based on the correct estimation it will help the

    software testing process with the perfect coverage.

    Functional point analysis is based on the analysis of

    user requirements of software with the various

    categories like outputs, inquiries, inputs, Internal files,

    External files.

    Test point analysis is used with estimation process for

    acceptance testing or black box.Software testing online

    courses explain clear concepts of testing.