Uploaded image for project: 'Qt Safe Renderer'
  1. Qt Safe Renderer
  2. QSR-1062

Refactor the manual testing related scripts



    • 1


      Do some refactoring

      • Separate the common functions from the testing logic
      • check if use of classes bring added value
      • check if event sender can log the info about used easing curves
      • fix the tabulation order for the test harness
      • remove magic numbers and parameterize those (or use global variables)
      • enable each supported property in the given safe QML type
      • configure if minimum or maximum amount of properties and features will be used (e.g. transition uses * or explicit state names)
      • make mutation easy for the input data (e.g. for fuzzing)
      • create data sets for positive and negative testing with equivalence classes
      • mention the assets in the safety manual, so that users can adapt those to testing their safety applications at need
      • etc

      Definition of Done:

      1. Test cases are in TestRail suites and plans
      2. Test code is reviewed
      3. Test code is in version control
      4. Test results are in TestRail


        No reviews matched the request. Check your Options in the drop-down menu of this sections header.



            qtsaferendererteam Qt Safe Renderer Team
            assaarel Asmo Saarela (Inactive)
            0 Vote for this issue
            1 Start watching this issue



              Gerrit Reviews

                There are no open Gerrit changes