AS-T12-Software development

checks if program performs as needed by customers before sign off; criteria is set and end user feedback is used to ensure criteria is met

• acceptance testing

• alpha testing

• beta testing

• white box testing

final round of testing;

users test under realistic conditions and feedback obtained;

checks if program meets requirements and performs as it should, problems reported to developer and corrected

• acceptance testing

• alpha testing

• beta testing

• white box testing

an individually tested module is joined to one program and tested to make sure modules interact correctly

• acceptance testing

• alpha testing

• white box testing

• integration testing

• stub testing

using a simple module, written to replace each subroutine, has simple output to show that a call is made; used when the actual module is not completed

• acceptance testing

• alpha testing

• white box testing

• integration testing

• stub testing

test where code is reviewed carefully by developers peers, managers, team members;

used to gather useful feedback to further develop code

• acceptance testing

• alpha testing

• walkthrough testing

• white box testing

• dry run testing

code is manually traced, value of variable is manually followed to check if it was used and updated as expected;

used to identify logic errors but not execution errors

• acceptance testing

• alpha testing

• walkthrough testing

• white box testing

• dry run testing

tests every path and every line of code using suitable test data;

tester views code

• acceptance testing

• blackbox testing

• walkthrough testing

• whitebox testing

• dry run testing

compares actual results of program being run to expected results, only considers input and output;

cannot view code

• acceptance testing

• blackbox testing

• walkthrough testing

• whitebox testing

• dry run testing

first round of testing;

software tested in house by dedicated testers, programmers who pretend to be users;

check requirements and deal with flaws

• acceptance testing

• alpha testing

• beta testing

• white box testing

examples of good programming practice

• sensible variable names

• using white spaces

• using indentations

• adding comments

• writing short code