Scribd
Upload
90 views3 pages

Testing

The testing phase involves completing various tests to ensure accurate code, expected functionality, and system interoperability. Thorough testing is critical to meeting requirements. Effective project management enhances testing by developing test plans early. Test plans help create detailed tests and increase the likelihood of identifying weaknesses. Testing groups perform staged tests in a top-down or bottom-up approach on representative test data to check components and systems. Primary tests include acceptance, end-to-end, functional, integration, parallel, regression, stress, string, system, and unit testing.

Uploaded by

Shelly
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
90 views3 pages

Testing

The testing phase involves completing various tests to ensure accurate code, expected functionality, and system interoperability. Thorough testing is critical to meeting requirements. Effective project management enhances testing by developing test plans early. Test plans help create detailed tests and increase the likelihood of identifying weaknesses. Testing groups perform staged tests in a top-down or bottom-up approach on representative test data to check components and systems. Primary tests include acceptance, end-to-end, functional, integration, parallel, regression, stress, string, system, and unit testing.

Uploaded by

Shelly
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

TESTING PHASE

The testing phase requires organizations to complete various tests to ensure the
accuracy of programmed code, the inclusion of expected functionality, and the
interoperability of applications and other network components. Thorough testing is
critical to ensuring systems meet organizational and end-user requirements.

If organizations use effective project management techniques, they will complete


test plans while developing applications, prior to entering the testing phase. Weak
project management techniques or demands to complete projects quickly may
pressure organizations to develop test plans at the start of the testing phase. Test
plans created during initial project phases enhance an organization’s ability to
create detailed tests. The use of detailed test plans significantly increases the
likelihood that testers will identify weaknesses before products are implemented.

Testing groups are comprised of technicians and end users who are responsible for
assembling and loading representative test data into a testing environment. The
groups typically perform tests in stages, either from a top-down or bottom-up
approach. A bottom-up approach tests smaller components first and progressively
adds and tests additional components and systems. A top-down approach first tests
major components and connections and progressively tests smaller components
and connections. The progression and definitions of completed tests vary between
organizations.

Bottom-up tests often begin with functional (requirements based) testing.


Functional tests should ensure that expected functional, security, and internal
control features are present and operating properly. Testers then complete
integration and end-to-end testing to ensure application and system components
interact properly. Users then conduct acceptance tests to ensure systems meet
defined acceptance criteria.

Testers often identify program defects or weaknesses during the testing process.
Procedures should be in place to ensure programmers correct defects quickly and
document all corrections or modifications. Correcting problems quickly increases
testing efficiencies by decreasing testers’ downtime. It also ensures a programmer
does not waste time trying to debug a portion of a program without defects that is
not working because another programmer has not debugged a defective linked
routine. Documenting corrections and modifications is necessary to maintain the
integrity of the overall program documentation.
Organizations should review and complete user, operator, and maintenance
manuals during the testing phase. Additionally, they should finalize conversion,
implementation, and training plans.

Primary tests include:

Acceptance Testing – End users perform acceptance tests to assess the


overall functionality and interoperability of an application.
End-to-End Testing – End users and system technicians perform end-to-end
tests to assess the interoperability of an application and other system
components such as databases, hardware, software, or communication
devices.
Functional Testing – End users perform functional tests to assess the
operability of a program against predefined requirements. Functional tests
include black box tests, which assess the operational functionality of a
feature against predefined expectations, or white box tests, which assess the
functionality of a feature’s code.
Integration Testing – End users and system technicians perform integration
tests to assess the interfaces of integrated software components.
Parallel Testing – End users perform parallel tests to compare the output of
a new application against a similar, often the original, application.
Regression Testing – End users retest applications to assess functionality
after programmers make code changes to previously tested applications.
Stress Testing – Technicians perform stress tests to assess the maximum
limits of an application.
String Testing – Programmers perform string tests to assess the
functionality of related code modules.
System Testing – Technicians perform system tests to assess the
functionality of an entire system.
Unit Testing – Programmers perform unit tests to assess the functionality of
small modules of code.
Within the automated testing world there are two
predominate testing methodologies: black-box and whitebox.

Black-box: This testing methodology looks at what are the


available inputs for an application and what the expected
outputs are that should result from each input. It is not
concerned with the inner workings of the application, the
process that the application undertakes to achieve a
particular output or any other internal aspect of the
application that may be involved in the transformation of an
input into an output. Most black-box testing tools employ
either coordinate based interaction with the applications
graphical user interface (GUI) or image recognition. An
example of a black-box system would be a search engine.
You enter text that you want to search for in the search
bar, press “Search” and results are returned to you. In such
a case, you do not know or see the specific process that is
being employed to obtain your search results, you simply
see that you provide an input – a search term – and you
receive an output – your search results.
White-box: This testing methodology looks under the
covers and into the subsystem of an application. Whereas
black-box testing concerns itself exclusively with the inputs
and outputs of an application, white-box testing enables
you to see what is happening inside the application. Whitebox
testing provides a degree of sophistication that is not
available with black-box testing as the tester is able to refer
to and interact with the objects that comprise an application
rather than only having access to the user interface. An
example of a white-box system would be in-circuit testing
where someone is looking at the interconnections between
each component and verifying that each internal
connection is working properly. Another example from a
different field might be an auto-mechanic who looks at the
inner-workings of a car to ensure that all of the individual
parts are working correctly to ensure the car drives
properly.

You might also like