Embed Size (px)
DESCRIPTION
Citation preview
Software TestingSoftware Engineering
Yasril SyafSHARING SESSION30 Desember 2011
Definition
bull Software testing is 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 programs on a computer All the associated tests are performed according to approved test procedures on approved test cases
bull Software testing is the process of exercising a program with the specific intent of finding errors prior to delivery to the end user
Software Testing
What Testing Shows
bull errorsbull requirements conformancebull performancebull an indication of quality
Who Tests the Software
Software Testing Strategies
Incremental testing strategiesndash Bottom-up testingndash Top-down testing
Big bang testingndash To test the software in its entirety once the completed
package is availablendash Unless the program is very small and simple application of
big bang testing strategies displays severe disadvantages 1048774Identification of error becomes quite cumbersome with respect to immense quantities of software
Top-down vs Bottom-up
Bottom-upndash Relatively easyndash Cannot observe the functions of the program until whole
modules have been integrated
Top-downndash Demonstrates the entire program functions shortly after
the upper-level modules have been completed 1048774early identification of errors in analysis and design
ndash Sometimes it is difficult to create the stubs since it is complicated 1048774have to provide varieties of functions
Classification of Software Testing
Black Boxbull Testing that ignores the internal mechanism of the system or
component and focuses solely on the outputs in response to selected inputs and execution conditions
bull Testing conducted to evaluate the compliance of a system or component with specified functional requirements
White Boxbull Testing that takes into account the internal mechanism of a system or
componentbull Testing conducted to evaluate the correctness of a system or
component by investigating the code structure (algorithm)
Black Box Testing
Black Box Testing
bull EC boundaries are defined by a single numeric or alphabetic value a group of numeric or alphabetic values a range of values and so on
bull Type of ECndash Valid ECndashAn EC that contains only valid statesndash Invalid ECndashAn EC that contains only invalid states
bull In cases where a programrsquos input is provided by several variables valid and invalid ECs should be defined for each variable
White Box Testing
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Definition
bull Software testing is 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 programs on a computer All the associated tests are performed according to approved test procedures on approved test cases
bull Software testing is the process of exercising a program with the specific intent of finding errors prior to delivery to the end user
Software Testing
What Testing Shows
bull errorsbull requirements conformancebull performancebull an indication of quality
Who Tests the Software
Software Testing Strategies
Incremental testing strategiesndash Bottom-up testingndash Top-down testing
Big bang testingndash To test the software in its entirety once the completed
package is availablendash Unless the program is very small and simple application of
big bang testing strategies displays severe disadvantages 1048774Identification of error becomes quite cumbersome with respect to immense quantities of software
Top-down vs Bottom-up
Bottom-upndash Relatively easyndash Cannot observe the functions of the program until whole
modules have been integrated
Top-downndash Demonstrates the entire program functions shortly after
the upper-level modules have been completed 1048774early identification of errors in analysis and design
ndash Sometimes it is difficult to create the stubs since it is complicated 1048774have to provide varieties of functions
Classification of Software Testing
Black Boxbull Testing that ignores the internal mechanism of the system or
component and focuses solely on the outputs in response to selected inputs and execution conditions
bull Testing conducted to evaluate the compliance of a system or component with specified functional requirements
White Boxbull Testing that takes into account the internal mechanism of a system or
componentbull Testing conducted to evaluate the correctness of a system or
component by investigating the code structure (algorithm)
Black Box Testing
Black Box Testing
bull EC boundaries are defined by a single numeric or alphabetic value a group of numeric or alphabetic values a range of values and so on
bull Type of ECndash Valid ECndashAn EC that contains only valid statesndash Invalid ECndashAn EC that contains only invalid states
bull In cases where a programrsquos input is provided by several variables valid and invalid ECs should be defined for each variable
White Box Testing
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Software Testing
What Testing Shows
bull errorsbull requirements conformancebull performancebull an indication of quality
Who Tests the Software
Software Testing Strategies
Incremental testing strategiesndash Bottom-up testingndash Top-down testing
Big bang testingndash To test the software in its entirety once the completed
package is availablendash Unless the program is very small and simple application of
big bang testing strategies displays severe disadvantages 1048774Identification of error becomes quite cumbersome with respect to immense quantities of software
Top-down vs Bottom-up
Bottom-upndash Relatively easyndash Cannot observe the functions of the program until whole
modules have been integrated
Top-downndash Demonstrates the entire program functions shortly after
the upper-level modules have been completed 1048774early identification of errors in analysis and design
ndash Sometimes it is difficult to create the stubs since it is complicated 1048774have to provide varieties of functions
Classification of Software Testing
Black Boxbull Testing that ignores the internal mechanism of the system or
component and focuses solely on the outputs in response to selected inputs and execution conditions
bull Testing conducted to evaluate the compliance of a system or component with specified functional requirements
White Boxbull Testing that takes into account the internal mechanism of a system or
componentbull Testing conducted to evaluate the correctness of a system or
component by investigating the code structure (algorithm)
Black Box Testing
Black Box Testing
bull EC boundaries are defined by a single numeric or alphabetic value a group of numeric or alphabetic values a range of values and so on
bull Type of ECndash Valid ECndashAn EC that contains only valid statesndash Invalid ECndashAn EC that contains only invalid states
bull In cases where a programrsquos input is provided by several variables valid and invalid ECs should be defined for each variable
White Box Testing
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
What Testing Shows
bull errorsbull requirements conformancebull performancebull an indication of quality
Who Tests the Software
Software Testing Strategies
Incremental testing strategiesndash Bottom-up testingndash Top-down testing
Big bang testingndash To test the software in its entirety once the completed
package is availablendash Unless the program is very small and simple application of
big bang testing strategies displays severe disadvantages 1048774Identification of error becomes quite cumbersome with respect to immense quantities of software
Top-down vs Bottom-up
Bottom-upndash Relatively easyndash Cannot observe the functions of the program until whole
modules have been integrated
Top-downndash Demonstrates the entire program functions shortly after
the upper-level modules have been completed 1048774early identification of errors in analysis and design
ndash Sometimes it is difficult to create the stubs since it is complicated 1048774have to provide varieties of functions
Classification of Software Testing
Black Boxbull Testing that ignores the internal mechanism of the system or
component and focuses solely on the outputs in response to selected inputs and execution conditions
bull Testing conducted to evaluate the compliance of a system or component with specified functional requirements
White Boxbull Testing that takes into account the internal mechanism of a system or
componentbull Testing conducted to evaluate the correctness of a system or
component by investigating the code structure (algorithm)
Black Box Testing
Black Box Testing
bull EC boundaries are defined by a single numeric or alphabetic value a group of numeric or alphabetic values a range of values and so on
bull Type of ECndash Valid ECndashAn EC that contains only valid statesndash Invalid ECndashAn EC that contains only invalid states
bull In cases where a programrsquos input is provided by several variables valid and invalid ECs should be defined for each variable
White Box Testing
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Who Tests the Software
Software Testing Strategies
Incremental testing strategiesndash Bottom-up testingndash Top-down testing
Big bang testingndash To test the software in its entirety once the completed
package is availablendash Unless the program is very small and simple application of
big bang testing strategies displays severe disadvantages 1048774Identification of error becomes quite cumbersome with respect to immense quantities of software
Top-down vs Bottom-up
Bottom-upndash Relatively easyndash Cannot observe the functions of the program until whole
modules have been integrated
Top-downndash Demonstrates the entire program functions shortly after
the upper-level modules have been completed 1048774early identification of errors in analysis and design
ndash Sometimes it is difficult to create the stubs since it is complicated 1048774have to provide varieties of functions
Classification of Software Testing
Black Boxbull Testing that ignores the internal mechanism of the system or
component and focuses solely on the outputs in response to selected inputs and execution conditions
bull Testing conducted to evaluate the compliance of a system or component with specified functional requirements
White Boxbull Testing that takes into account the internal mechanism of a system or
componentbull Testing conducted to evaluate the correctness of a system or
component by investigating the code structure (algorithm)
Black Box Testing
Black Box Testing
bull EC boundaries are defined by a single numeric or alphabetic value a group of numeric or alphabetic values a range of values and so on
bull Type of ECndash Valid ECndashAn EC that contains only valid statesndash Invalid ECndashAn EC that contains only invalid states
bull In cases where a programrsquos input is provided by several variables valid and invalid ECs should be defined for each variable
White Box Testing
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Software Testing Strategies
Incremental testing strategiesndash Bottom-up testingndash Top-down testing
Big bang testingndash To test the software in its entirety once the completed
package is availablendash Unless the program is very small and simple application of
big bang testing strategies displays severe disadvantages 1048774Identification of error becomes quite cumbersome with respect to immense quantities of software
Top-down vs Bottom-up
Bottom-upndash Relatively easyndash Cannot observe the functions of the program until whole
modules have been integrated
Top-downndash Demonstrates the entire program functions shortly after
the upper-level modules have been completed 1048774early identification of errors in analysis and design
ndash Sometimes it is difficult to create the stubs since it is complicated 1048774have to provide varieties of functions
Classification of Software Testing
Black Boxbull Testing that ignores the internal mechanism of the system or
component and focuses solely on the outputs in response to selected inputs and execution conditions
bull Testing conducted to evaluate the compliance of a system or component with specified functional requirements
White Boxbull Testing that takes into account the internal mechanism of a system or
componentbull Testing conducted to evaluate the correctness of a system or
component by investigating the code structure (algorithm)
Black Box Testing
Black Box Testing
bull EC boundaries are defined by a single numeric or alphabetic value a group of numeric or alphabetic values a range of values and so on
bull Type of ECndash Valid ECndashAn EC that contains only valid statesndash Invalid ECndashAn EC that contains only invalid states
bull In cases where a programrsquos input is provided by several variables valid and invalid ECs should be defined for each variable
White Box Testing
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Top-down vs Bottom-up
Bottom-upndash Relatively easyndash Cannot observe the functions of the program until whole
modules have been integrated
Top-downndash Demonstrates the entire program functions shortly after
the upper-level modules have been completed 1048774early identification of errors in analysis and design
ndash Sometimes it is difficult to create the stubs since it is complicated 1048774have to provide varieties of functions
Classification of Software Testing
Black Boxbull Testing that ignores the internal mechanism of the system or
component and focuses solely on the outputs in response to selected inputs and execution conditions
bull Testing conducted to evaluate the compliance of a system or component with specified functional requirements
White Boxbull Testing that takes into account the internal mechanism of a system or
componentbull Testing conducted to evaluate the correctness of a system or
component by investigating the code structure (algorithm)
Black Box Testing
Black Box Testing
bull EC boundaries are defined by a single numeric or alphabetic value a group of numeric or alphabetic values a range of values and so on
bull Type of ECndash Valid ECndashAn EC that contains only valid statesndash Invalid ECndashAn EC that contains only invalid states
bull In cases where a programrsquos input is provided by several variables valid and invalid ECs should be defined for each variable
White Box Testing
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Classification of Software Testing
Black Boxbull Testing that ignores the internal mechanism of the system or
component and focuses solely on the outputs in response to selected inputs and execution conditions
bull Testing conducted to evaluate the compliance of a system or component with specified functional requirements
White Boxbull Testing that takes into account the internal mechanism of a system or
componentbull Testing conducted to evaluate the correctness of a system or
component by investigating the code structure (algorithm)
Black Box Testing
Black Box Testing
bull EC boundaries are defined by a single numeric or alphabetic value a group of numeric or alphabetic values a range of values and so on
bull Type of ECndash Valid ECndashAn EC that contains only valid statesndash Invalid ECndashAn EC that contains only invalid states
bull In cases where a programrsquos input is provided by several variables valid and invalid ECs should be defined for each variable
White Box Testing
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Black Box Testing
Black Box Testing
bull EC boundaries are defined by a single numeric or alphabetic value a group of numeric or alphabetic values a range of values and so on
bull Type of ECndash Valid ECndashAn EC that contains only valid statesndash Invalid ECndashAn EC that contains only invalid states
bull In cases where a programrsquos input is provided by several variables valid and invalid ECs should be defined for each variable
White Box Testing
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Black Box Testing
bull EC boundaries are defined by a single numeric or alphabetic value a group of numeric or alphabetic values a range of values and so on
bull Type of ECndash Valid ECndashAn EC that contains only valid statesndash Invalid ECndashAn EC that contains only invalid states
bull In cases where a programrsquos input is provided by several variables valid and invalid ECs should be defined for each variable
White Box Testing
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
White Box Testing
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
White box testingPath coverage vs Line coverage
Path Coveragebull Path coverage of a test is measured by the percentage
of all possible program paths included in planned testing
Line Coveragebull Line coverage of a test is measured by the percentage
of program code lines included in planned testing
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Testing process
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Determining the test methodology
Testing strategyndash Big-bang
ndash Incrementalbull Top-downbull Bottom-up
Which part usingndash White-box testingndash Black-box testing
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Planning the test
bull What to testndash Which modules which integrations priorities
bull Which sourcesndash Real test casendash Synthetic test case
bull Who performsndash Integrationunit tests ndashgenerally by development teamndash System tests ndashusually by independent teamndash For large scale software ndashmore than one team
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Planning the test (2)
bull Where to performndash Developerrsquos sitendash Consumerrsquos sitendash Independent site
bull When are tests terminatedndash The completed implementation routendash The mathematical models application routendash The error seeding (hidden) routendash The dual independent testing teams routendash Termination after resources have run out
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Designing test
bull Software test plan (STP)Contains the plan of testingndash Scopendash Testing environmentndash Test detailsndash Test schedule
bull Software test descriptions (STD)ndash Contains the procedures of testing which consists of
document test procedure and test case file
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Test implementation
bull Running the test casesbull Documenting the testrsquos resultsbull Re-testing (regression test) to verify the
correction of errors
Terima Kasih
bull QA
Terima Kasih
bull QA
![Testing Evolving Software - uni-saarland.de · Testing Evolving Software Software Engineering Static/Dynamic Program Analysis, Software Testing, Security Tuesday, June 22, 2010 [...]](https://img.dokumen.tips/doc/110x75/5e87dad78a1ee05738317409/testing-evolving-software-uni-testing-evolving-software-software-engineering.jpg)
