software testing approaches

A bug is error in an algorithm or program.

• True
• False

Why is it important to test software?

• To make sure the designer is charging enough for their work

• To make sure that the final system meets user requirements

• To make sure that some of the user requirements have been met

• To identify programming errors so that sloppy programmers can be fired

Should all systems be tested before going 'live'?

• Yes

• No

During system testing, the system tester(s) should (select all that apply):

• Report bugs to the development team for correction

• Order tea, coffee and lunch for the system team

• Detect and fully document any bugs encountered, with screenshots

• Ensure all user requirements were considered

In iterative testing, testing takes place during the build. True or False?

• True

• False

What is an advantage of carrying out testing during the development process?

• earlier detection of errors

• costs will go up

• project will take longer to finish

What do you call the person responsible for testing?

• Source Tester

• System Tester

• Program Tester

• Bug Destroyer

What does the term 'System Lifecyle' mean?

• how long an application or system is built to last

• how longs it takes to build a system

• the time it takes to complete a system from analysis to evaluation

A software testing method in which the functionalities of software applications are tested . There is no need to have knowledge of the internal code.

• Black Box

• Grey Box

• white Box

• Green Box

Beta Testing is done at:

• Developer’s end

• User’s end

• User’s & Developer’s end