Take a Step Forward: 044-42328182, 9940289059, 99520 47742

Take a step forward

044 4232 8182  |  099402 89059  |  098406 73836   |   099404 61014

IAO Logo
testing training best curriculum, best fees, best placement
testing training placement

FAQ - Frequently Asked Questions

Why software needs to be tested?

Every software product needs to be tested since, the development 'process' is unable to produce defect free software. Even if the development process is able to produce a defect free software, we will not be able to know unless & until we test it. Without testing it, we shall not be having enough confidence that it will work.

Testing not only identifies and reports defect but also measures the quality of the product, which helps to decide whether to release the product, or not. The process of identifying the defect or a mistake in a product or a process is termed as "Testing"

For who software testing will be a good career option ?

Software testing offers you opportunity to fully utilize your critical thinking to discover that others do not see. You have to think out of the box- think of things and situations that others have overlooked. If those elusive bugs were easy to find, they probably wouldn't be there. It is less technological focused than software development, but it does not mean inferiority.

You don't have to be a programming enthusiast to be a good software test engineer. But you have to have good analytical and creative skills, which you can also develop further in this profession.

Any graduate who does not want to be involved in programming can opt for software testing as their career option. The software testing training in Chennai provided by Accord offers simple and best syllabus for you to be industry ready.

What is Software Development Life Cycle "SDLC" ?

SDLC means "Software Development Life Cycle" is a software development process, used by a systems analyst to develop an information system. Here the product or a process will follow the step by step activity in developing the end product to the user. It starts with activities like:

  1. Requirement Analysis:
    1. Project Initiation
    2. Requirement Gathering and Documenting
  2. Designing:
    1. High Level Design (Communication Approach and Data Flow Approach)
    2. Low Level Design (Internal logic of the process)
  3. Coding: Implements the internal logic with the programming structure of a process
  4. Testing:
    1. Integration Testing
    2. System Testing
  5. Implementation: This phase carries over the Installation and Acceptance Testing
  6. Support or Maintenance: it deals with the issues related to the current project and the enhancements with the requirements to be included for the project.

Why do we Need testing technique ?

When the functional specification of the requirement is tested, the features to be tested will carry over with both positive testing and the negative testing.

"Positive testing" it carries over the feature of testing the content which is present in the SRS. "Negative testing" it carries over the feature of testing the content which is not present in the SRS. So for the entire needed requirement both positive and negative testing should be conducted by the user for the entire test process.

In Such cases, the functional specification of the object is declared with the limits or ranges, then testing all the value within range and outside of the range is completely impossible working with the real time. Now to reduce the number of test cases for the specification drastically for the condition, the testing techniques can be used.

What is System Testing Life Cycle "STLC" ?

System testing life cycle follows the various stages in testing the functional specification of a requirement. It follows the step by step activity so that the behavior is tested with identifications of a bug.

  1. Requirements Document
  2. Preparation of Test Plan
    Test Plan: Test plan is the document where the roadmap for the entire test activity will be jotted in a sequential manner.
  3. Preparation of Test Cases:
    Test Cases: It is a step by step procedure used to identify whether the given requirement produces defects or not. It follows the template of developing the test process.
    The basic test case template consists of the following fields: test case id, test case Description, test case procedure, Sample input data, Expected Result, Actual Result and Status. During the preparation of the test cases, the template will be filled only till the expected result.
  4. Execution of Test Cases:
    Once the execution is carried over with the prepared test cases, the actual result and the status of the requirement will be filled.
  5. Preparation of the Test Log:
    Test Log: It is a template where it contains the details of the test cases which moves on to the both pass and fail status. It used to evaluate the test estimation of the process.
  6. Reporting of Bugs:
    Defect Report: It’s a report where it contains the details of the test case which moves on to the fail status. The bugs will be identified and followed by using the bug life cycle for tracking unless it is resolved.
  7. Test Report Generation:
    The final test report is generated with eight interim graphs, where the entire closure activity is carried over by handling the test activity.