10

Click here to load reader

Software testing (strategies)

Embed Size (px)

Citation preview

Page 1: Software testing (strategies)

Luthfiya Ulinnuha - 5209100115

Page 2: Software testing (strategies)

• a formal process carried out by a specialized testing team in which a software unit, several integrated software units or an entire software package are examined by running the programson a computer.

• All the associated tests are performed according to approved testprocedures on approved testcases.

Page 3: Software testing (strategies)

• To identify and reveal as many errors as possible in the tested software.

• To bring the tested software, after correction ofthe identified errors and retesting, to an acceptable level of quality.

• To perform the required testsefficientlyand effectively, within budgetary and scheduling limitations.

Page 4: Software testing (strategies)

Black Box (functionality) testing

• Identifies bugs only according to software malfunctioning

White box (structural) testing •Testing that takes into account the internal mechanism

ofa system or component.

According to testing concept

Page 5: Software testing (strategies)

• Black box classified into 3 classes

a. Operation factor testing classes

b. Revision factor testing classes

c. Transition factor testing classes

Page 6: Software testing (strategies)

(1)Output correctness tests– in most cases, the class of tests that consume the largest weight of testing resources

(2)Documentation tests(for correctness)

(3)Availability(reaction time) tests(for correctness)

(4)Reliabilitytests

(5)Stresstests(load tests, durabilitytests) (for efficiency)

(6)Software system securitytests

(7)Training usability tests(for usability)

(8)Operational usability tests(for usability).

a. Operation factor testing classes include:

Page 7: Software testing (strategies)

(1)Maintainabilitytests

(2)Flexibilitytests

(3)Testabilitytests.

b. Revision factor testing classes include:

Page 8: Software testing (strategies)

(1)Portability tests

(2)Reusability tests

(3)Software interfacing tests(for interoperability)

(4)Equipment interfacing tests(for interoperability).

c. Transition factor testing classes include:

Page 9: Software testing (strategies)

According to requirement

Page 10: Software testing (strategies)

• Path coverage is defined as the percentage of possible path sofsoftware processing activated by the test cases

• Line coverage is defined as the percentage of executed lines of code examined during the tests.