Fundamental Test Process:

This is the process of planning of test stage or process, what we do before

the other. It is divided into the following.
1) Planning and control.
2) Analysis and Design.
3) Implementation and Execution.
4) Evaluating exit criteria and reporting.
5) Text closure activities.

Planning and control.

During test plan we make sure that we understand the goals and objective
customer, stakeholder, and general project and more especially the risk
which the testing is going to address, most time it is called the mission of
testing, during test planning the following steps and document will be
address.
Test Plan:
A document describing the scope, approach, resources schedule of test
activity, identify test item, feature to be tested, the testing task, degree of
tester independence, the test design technique. it is a record of the test
plan from beginning to the end.

Test Policy:
This is organization document regarding, the principle, approach objective
and rules in testing.
Test Strategy:
level description of test to be perform, as a whole or within test.
Test Coverage:
The degree express as % to which a specified coverage item has been
exercised by a test suite.
Exit Criteria:
The set of generic and specific condition, agreed upon with stakeholders
for permitting a process to be officially completed. It is use to know when
to stop testing.
Test Control:
A test management task aim at developing and applying corrective
measures and actions to get a test project back on track when monitoring
shows deviations
Test Monitoring:
A test management task that deal with activities relating to periodically
checking the status of test project.
Test Basis:
All documents from which the requirement of a component or a system
can be inferred, the documentation on which the test cases are base.

Test Analysis and Design:

This is a set of activities where test objective are transform to into
tangible test condition and test design, all objective identified during
planing will be put into procedure to actually test the software, the
following activities are done at this stage:

1) Review test basis:

The following documents could be reviewed, risk analysis, design

specifications, interface, after this reviews certain type of test could be
use (Black box testing), even if there is no code. As we impliment this,
Gaps, ambiguities in the specifications will be identify.as we use the
documents we begin to understand what the software should do.

2) Identify Test condition:

Base on the reviw of the test documents, we begin to understand the

behaviour of the software or systems, this will give us a list of what we
should be interested in testing, we begin to make condition for “pass” or
“failed” . the type of input and espected output data input and expected
output is establised, use of indicators, what will be the pass or failed
expectations will be stated. From here we know the data we will use.

3) Test case:

A set of input, values, execution, expected result developed for a

particular test, eg check a particular program “play ” button whether it
comply to trigering the media player to play.

4) Test Design Specification:

A documents specifying the test condition(coverage items) for a test item,

detailed test approach and the high level test case. Aspect of the software
which carry risk will be identify

5) Design Test Environment:

Set up and identify any required infrastructure and tools , support tools
such as spreadsheet, word processor, project planning tools and non-IT
Tools and equipments, infact verything we need.
Implementation and Execution:
Test condition is made into test cases, testware and the Environment is
set up,

Me start making test procedure and script for automation, we set up

where to run the test and build test data. The task is as follows

Implementation:

Develop and prioritize the test cases, instruction for carrying out the
test(test procedure )will be written, we may write were to automate the
test. We create a test suite. Check to make sure that test environment a
set up properly.

Execution:

I. Execute the test suite and individual test cases following the procedure, it
might be manual or automated according to the planned sequence.

II. Log the out come of test execution and record the identities version of the
software under test, using test log

III. Compare the result with expected result

IV. Repeat the test activities as a result actions or failures (confirmation or re-
testing), even performing regression testing where a bug has been fixed.

Evaluating exit criteria and reporting.

Is done when the test execution is assessed against the objective, it must
be done for each test level, to establish if we have done enough testing,
we have a set criteria to which we measure enough, and this is base of
the set objective, risk assessment. The major task are carried out.
I. Check test log against exit criteria specify in planning.
II. Assessed if more test is needed.
III. Write a test summary report

Text closure activities.

Data are collected for test result for training and experience, for writing
the final of the software documentations.
Test closure could be also that the project is stopped or enough test has
been done to satisfy the stakeholders, the following is a major output in
closure;
I. Check planned deliverable according to the planned objective,
incident report from the log showing defect has been corrected
 II. Finalize and archive the test ware such as script, test environment,
test infrastructure, for test reuse during maintenance testing.
III. Hand over test ware to maintained organizations
IV. Evaluate how test went and document the lesson learnt.

Psychology of Software Testing:

Independence is the separation of responsibility to encourage the
accomplishment of test objective, notice that testing are carried out by
different group of people see below
The independence of testing is essential for quality of test; though it is
often regarded in some circle that the more independent the better, below
is the rank of the independence from lowest to highest
1) Test by people/person that wrote the item to be tested
2) Test by another person within the same team.
3) Test by persons from different organization like independent test
team professionals
4) Test design and carried out by person from different organization or
totally external.

Due to independence in testing there are always tensions between testing

team that developers, since is as the testing team is always there to find
the fault. To diffuse the tension the following is suggested.
1) Communicate find on the product as neutral as possible
-don’t gloat
-don’t blame
-log it without as much neutral a language as possible.

2) Start with corporations collaborations rather than division

3) Offer any explanations to show that anybody could review your work
if there want.
4) Always show team work.