Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Reviewing and improving this test plan - particularly by integrating aspects of the https://docs.google.com/document/d/1hJNOaElk9aP9SNgnHA_eZOynAMb3Kvo_pzCwofbRHEQ/edit and ensuring it covers that

  2. Documenting the test objectives as requirements in PractiTest [currently, this is done for the mvp using the tags: mvp, safe_places]

  3. Designing tests in PractiTest (mapped to requirements)

  4. Executing tests and raising issues in GitHub

  5. Determining the right automation tools

  6. Implementing automation tests

...

  • Verify the ability to combine files in the publisher.  

  • Verify that the publisher does not crash / hang / become unresponsive [Note: I don’t believe there are volumetrics for this, I would assume that a HA could be combining hundreds of files with hundreds of data points]

  • Verify that none of the data is sent to any 3rd party endpoints

  • Verify the functionality is the same in popular modern browsers (Chrome, Safari, Edge)

  • Verify the accuracy of data presentation and time filtersVerify that the combined files are exported together

  • Verify that the application will not crash if invalid or very short/long values are entered in free text fields

  • Validate that common errors a CT may make result in sensible error messages

  • Validate the automatic zoom functionality

...