Looking for best Software Testing Training in Chennai? 7pixelz is the No 1 Software Testing Training Institute in Chennai .These institute offering professional training on both Manual testing and automation testing. Automation testing training like Selenium. Call +91 7200037781 for Software Testing Training course details.

Software Testing

Software Testing is checking using the functions and features of anapplication created by the development team, to ensure that which is this working as per the requirement specification of the Customer. This is called as "Software Testing".

Who can test the software?

Once the requirement has been obtain from the customer. After the development team understanding in to the requirement of the coding and creating the software. Than developing team will be given to testing team. After the testing team checking the software working properly or not. Developer, Tester and Customer all three can to the testing.

Why do we need separate testing team to testing the software?

Developers will think in signle point of view, where as the testing engineer should be thinking from mulitiple point of view.

Understanding the CRS by the developer might be tn wrong perspective and hence if same person do the testing, the same wrong software might be the output. So, when the testing person is working in he may arrive at right one.

Time taken for the delivery increases if same person do the developing, testing and fixing issues. So to reduce the turnaround time for the delivery of the software to the customer, we need to have work allocation between teams.

Developers may be over confident and they may be end up without finding issues.

Types of Software Testing

Two different types of testing. There are,
1. Manual Testing
2. Automation Testing

Manual Testing

Understanding the requirements and testing the application by entering the test cases manually. This is known as manual testing.

Test Case

Test case is an one of the document, which is consist of instruction or procedure to verify the functionality of the an application. These instruction or procedure are prepared based on understanding the CRS.

Automation Testing

  • Automation Testing is a process of converting manual test case into automation test scripts or program by using a tool. Which the application is tested in automation testing.
  • No manual effort is used, by using a tool they used to test an application.
  • What is test script?

  • Manual test cases is converted into a script (or) program is known as “test script”.
  • Test script is a script or program to check the application automatically.
  • Why should we go for automation testing?

  • Repeatability is high
  • Build should be stable.
  • For example: Calculator function in windows vista, XP, windows7, windows8.
  • Advantages of automation testing?

  • We go for automation testing because it avoid manual efforts.
  • Time taken to test the software decreases.
  • Cause effective.
  • Accuracy.
  • Highly reliable (Every instance it check all conditions).
  • Upgradation
  • Consistance
  • What is SDLC?

    Systematic procedure followed in order to create a software is known as SDLC. (Software development life cycle)

    Note: It can also be defined as different style (or) the way we going to follow to create a software

    Some commonly used SDLC model

  • Water fall Model
  • Spiral Model (or) Iterative Model
  • Prototype Model
  • V Model
  • Agile Methodology
  • Methods of testing

    1. White box testing.
    2. Grey box testing.
    3. Black box testing.

    White box testing

  • It is a testing done by the development team after the completion of coding by looking into the internal behavior of the code.
  • Majorly WBT is done by developers.
  • Note: Internal behavior means logic of the code or flow of the code.

    Black box testing

  • It is a testing done by the professional testing engineer by looking into the application. They do not have any access to the logic of the code (or) flow of the code.
  • BBT can be done by developer, testing engineer, customer. But professionally only testing engineer can own BBT.
  • Grey box testing

  • It is the combination of both WBT and BBT, where the testing engineer (or) developers will be looking into the high level database diagram and data flow diagram and proceed the testing activity.
  • Mostly used in complex projects. They get more into integration level.
  • Why the name WBT, GBT, BBT?

  • WBT is transparent (Example: water). Clear access through the source code of application.
  • GBT is translucent (Example: water). Partial access.
  • BBT is opaque (Example: not visible). Do not have access to the source code of application.
  • What is Retesting? Example?

    The testing team executes the test case for the first time and they find the application is not working properly so they report the issues to the development team. The development team fixes the issues and provide the fixes in the new build. The testing team installs the new software and the same failed test cases is retested on the new build. To check the failed test cases is working properly or not. If it is failed, again the process continues. If it get passed then it moved to next stage.

    Example: take any feature which not works initially and after a fix by developer it works properly

    Manual Testing Course Syllabus:

    Introduction to Testing

    Why Testing
    STLC – Software Testing Life Cycle
    Verification and Validation
    Desktop, Web and Mobile Applications Testing

    Software Developing Lifecycle Models

    Waterfall model
    Spiral model
    Prototype model
    V model
    Agile Methodology

    Test Strategy & Test Planning with a Live Project

    Working on Test Strategy
    Preparing Test Plan document
    Clarification Document
    Getting Familiar with Test Design

    Preparing a Test Case Document

    Boundary Value Analysis (BVA)
    Equivalence Partitioning (EP)
    Decision Table Testing
    State Transition Diagrams
    Use Case Testing
    Statement Coverage
    Branch Coverage
    Path Coverage
    LCSAJ Testing

    5.Executing Test Cases

    6.Test Reporting

    7.Defects Tracking Mechanism and Life Cycle

    8.Defect Categorization

    Guidelines On Deciding The Security Of A Defect
    Guidelines On Deciding The Priority Of Bug
    Cost of Quality
    Defect Management with Tools like Bugzilla
    Static Testing
    Dynamic Testing
    White Box Testing/ Structure Testing
    Black Box Testing

    Types Of Testing – Functional Testing:

    Unit Testing
    Integration Testing
    Smoke Testing
    System Testing
    Regression Testing
    User Acceptance Testing
    Globalization Testing
    Localization Testing

    Types Of Testing – Non Functional Testing:

    Performance Testing
    Compatibility Testing
    Data Migration Testing
    Data Conversion Testing
    Security/Penetration Testing
    Usability Testing
    Install/Un-Install Testing

    Have questions on Manual testing training? We are happy to help!