Chapter 16

• A/B testing


  End users are presented with different versions of a digital application; statistical analysis is carried out to determine which is most successful.
• alpha testing


  involves stimulating the real-world environment the application has been designed for, normally carried out by just a small number of users prior to beta testing
• beta testing


  Carried out just after alpha testing and before the final version of the application is released commercially
• black box testing


  where the tester is unaware of the internal structure of the application they are testing
• bugs


  another word for error or fault which leads to errors in the execution of a program or application
• dry run


  A paper-based exercise which allows the programmer to go through the solution step by step. The dry run will highlight any errors in the logic of the solution.
• extreme data


  Used to test that the system can cope with very large or very small data values
• iterative development approach


  A step-by-step approach taken to the development of an application. Each step sees the life-cycle of analysis, design, development, testing, installation and review being repeated, each time adding more and more to the application until it is eventually completed
• null data


  used to test that the system can cope when no data is entered
• robustness


  a measure of the systems ability to continue to run when high volumes of valid, exceptional or invalid data is entered
• system testing


  Carried out on a completed and fully integrated system to ensure correct outputs are produced in compliance with the user requirements document.
• testing evidence


  Documentation which illustrates the outcome of tests applied to application software, this may be in the form of annotated screenshots.
• trace tables


  Created during a dry run containing all data items and output used in the section of code being reviewed. The value of each data item is documented after each line of the solution is executed.
• waterfall model


  represents a sequential approach to application development. A series of stages need to be completed in a fixed order and each stage must be completed before the next can begin
• white box testing


  A method of testing which examines the underlying structure of the application or code which has been developed.
• the development process is the term to describe what


  the stages involved in the development of a new software application
• the waterfall model takes what kind of approach

  sequential
• Waterfall Model Phases


  analysis

  design

  implementation

  testing

  installation

  review
• what does the iterative development approach encourage


  the development team to break down the development of the application into smaller more manageable tasks
• how does the waterfall model differ from the iterative development process


  in the iterative development process each task undergoes its own development life cycle
• what does the repeated of the system life cycle following each iteration means what


  errors are detected at the early stage of development
• what is the 3 responsibilities of the system tester


  test plans should be well prepared and reviewed on an ongoing bases

  
  

  the testing team must take the user requirements into consideration when developing test plans

  
  

  any bugs detected during the testing process should be well documented and reported to the developer
• what does testing help do during the development process


  identify and correct errors in the application being developed
• the role of testing during the development process helps the developer assess what


  assess the reliability of the application and ensure it works
• a well tested application will help to ensure...

  the production of a high quality application which meets the user requirements previously identified by the client
• testing as part of the waterfall model


  testing does not take place until the system has been designed and implemented

  once an application has been developed if an error is detected at the testing stage it can be difficult to make changes
• testing during iterative development approach


  tests are carried out at each stage of development of the application

  this ensures the bugs are corrected at an early stage in development

  errors are detected easily on and are easier to correct

  reduces the cost of correction and in turn keep overall development costs low

  less likely anything is left out
• features of an effective test plan


  This will ensure any errors in the application are detected this may involve debugging areas of the application or identifying omissions in the application in relation to user requirements.

  testing can be conducted at any stage of the development however for it to be carried out effectively it must be well planned and documented
• the expected content of a test plan are


  introduction

  test approach

  test strategy
• introduction


  summary of the application or a particular area of the application to be tested
• testing approach


  a wide range of testing can be applied by the testing team and the methods chosen will depend on the type of application being developed
• black box testing


  the design or structure of the application being tested is unknown to the person conducting the tests

  the name comes from that the tester approaches the system as a black box they cant see into

  the aim of this is to identify the errors which relate to general interface or operation of the application such as incorrect buttons

  the data is developed on based upon the user requirements
• white box testing


  allows the testing team to examine the underlying structure of the application

  
  

  in order to carry out this testing effectively a detailed knowledge of the development environment is needed

  
  

  specific inputs are selected to ensure all appropriate pathways through the application are examined and ensure the correct output is produced

  
  

  tests are often applied to code that is being executed, the code may also be examined manually using a process called dry run
• what are trace tables


  Trace tables allow the testing team to examine the contents of any variables manipulated or outputs generated as the extract of code is executed
• system testing


  carried out when all individual components or parts of an application have been developed and fully tested as standalone elements

  helps ensure all individual components work together to produce the correct outputs as identified in the user requirements document
• alpha and beta testing


  forms a developmental testing where the outcome of the testing process can be used to support the continued development of the application

  
  

  carried out on versions of the application not yet completed

  
  

  their aim is to detect any bugs in the system which have so far gone undetected
• alpha testing


  normally carried out by a small number of users not previously involved in the development process

  involves simulating the real world environment the application has been designed for
• beta testing


  represents the final stage in testing and is carried out just before the final version of the application is released commercially

  often the application will be sent out in the form of a free trial version for download across the internet in hope any errors will be detected reported and corrected to the commercial release of the application
• A/B testing


  the release of more than one version of an application to see which one is preferred by the target audience e.g. two versions of a digital application are created and released to the general public

  one half will be presented to the original version and the second with a modified version of the application

  statistical analysis will be carried out to help determine the impact any changed had on the success of the application
• multimedia testing


  multimedia applications should be tested to ensure they run efficiently on more than one platform