Testing and Evaluating Software Solutions Introduction

Gantt Chart

Using the Gantt Chart Enter ‘Actual Start’ when you begin a task Update ‘Percent Complete’ as you progress through a task When you finish a task, set ‘Percent Complete’ to 100% and enter ‘Actual Finish’

Class Discussion What is testing? Why do we test? Where have you used testing previously? Software or otherwise.

Formal Testing Is integral to all stages of the software development cycle, comprised of two phases: alpha and beta Is the central process to ensure that software meets the original objectives and design specifications; quality assurance Tools available to automate and report on the testing process

Alpha Testing Testing of the final solution by personnel within the software development company prior to the product’s release Real data is used

Beta Testing Testing of the final solution by a select number of users outside the software development company using real world data and conditions Occurs when the product is distributed to external users who are enlisted to report any faults

Techniques for testing the objectives There are two techniques that have the purpose of identifying and correcting errors: – Black box testing – White box testing Black box testing or functional testing is where the inputs and expected outputs are known; the processes occurring are unknown. White box testing or structural testing is the testing technique explicit knowledge of the internal workings of the item being tested is used

Readings and Activities Read pages of the textbook Complete Question 11 on page 246 of the textbook