Life Cycle testing-Role of Testers,Test Plan,TestCase

Life Cycle testing-Role of Testers

Concept Phase:

Evaluate Concept Document,

Learn as much as possible about the product and project

Analyze Hardware/software Requirements,

Strategic Planning

Requirement Phase:

Analyze the Requirements

Verify the Requirements using the review methods.

Prepare Test Plan

Identify and develop requirement based test cases

Design Phase:

Analyze design specifications

Verify design specifications

Identify and develop Function based test cases

Begin performing Usability Tests

Coding Phase:

Analyze the code

Verify the code

Code Coverage

Unit test

Integration & Test Phase:

Integration Test

Function Test

System Test

Performance Test

Review user manuals

Operation/Maintenance Phase:

Monitor Acceptance Test

Develop new validation tests for confirming problems

Software TESTING

Test plan:

A test plan is a systematic approach to testing a system such as a machine or software.The plan typically contains a detailed understanding of what the eventual work flow will be (or)

The test plan defines the objectives and scope of the testing effort, and identifies themethodology that your team will use to conduct tests. It also identifies the hardware, software,and tools required for testing and the features and functions that will be tested. A well-roundedtest plan notes any risk factors that jeopardize testing and includes a testing schedule(or)

A test plan is a document describing the scope, approach, resources,andschedule of intended test activities. It identifies test items, the features to betested,the testing tasks, who will do each task, and any risks requiringcontingency plans. An important component of the test plan is the individualtest cases. Some form of test plan should be developed prior to any test.

TESTCASE:

A test case is a set of test inputs, execution conditions, and expected results to determine if a feature of an application is working correctly, such as to exercise a particular program path or to verify compliance with a specific requirement. Think diabolically! What are the worst things someone could try to do to your program? Write test for these.

Testing process:

The test development life cycle contains the following components/steps:

• System study-Assess development plan and status

• Collect SFS/SRS

• Develop Test plan

• Design test cases

Tests specifications: This document includes technical details ( Software requirements )required prior to the testing.

• Execute tests

• Evaluate tests

• Evaluate results

• Acceptance test

• Document results(defect reports, summary reports)

Recreating the problem is essentially important in testing so that problems that are identified can be repeated and corrected.

Testing strategy:

Test Strategy provides the road map describing the steps to be undertaken while testing, and the effort, time and resources required for the testing.

The test Strategy should incorporate test planning, test case design, test execution, resultant data collection and data analysis.

Monkey Testing:

Testing the application randomly like hitting keys irregularly and try to brake down the system there is no specific test cases and scenarios for monkey testing Verification refers to set of activities that involves reviews and meetings to evaluate documents, plans, code, requirements and specifications(to ensure that software correctly implements a specific function, imposed at the start

of that phase); this can be done with checklists, issues lists, and walkthroughs and inspection meetings.

For example, in the software for the Monopoly game, we can verify that two players cannot own the same house. Validation is the process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements. (or)

Validation refers to a different set of activities that the software that has been built is traceable to customer requirements

For example, we validate that when a player lands on “Free Parking,” they get all the money that was collected. validation always involves comparison against requirements.

In the language of V&V, black box testing is often used for validation (are we building the right software?) and white box testing is often used for verification (are we building the software right?).

Quality Assurance (QA) The system implemented by an organization which assures outside bodies that the data generated is of proven and known quality and meets the needs of the end user. This assurance relies heavily on documentation of processes, procedures, capabilities, and monitoring of such.

• Helps establish processes
• Identifies weaknesses in processes and improves them
• QA is the responsibility of the entire team Quality Control (QC) Mechanism to ensure that the required quality characteristics exist in the finished product (or) It is a system of routine technical activities, to measure and control the quality of the product as it is being developed.Quality control activities may be fully automated, entirely manual, or a combination of automated tools and human interaction
• implements the process.
• Identifies defects for the primary purpose of correcting defects.
• QC is the responsibility of the tester.

                                                          PREVIOUS