Skip to content
This repository was archived by the owner on Nov 7, 2018. It is now read-only.

Phase 2 testing

Jump to bottom
siwhitehouse edited this page Nov 16, 2012 · 6 revisions

The second phase of AidView has introduced a new set of data elements from the IATI activity standard, along with some new functions such as the ability to print an activity datasheet and export an activity file to comma separated variable (csv) format.

As different funders have created their files in different ways, it makes sense to test one or more of each funder's files against the new data elements and functions to see that they perform as expected. The AidView Testing matrix can be used to systematically work through funders and test this.

Method

  1. Go to the AidView v2 test environment
  2. Choose a funder and then one of their activities
  3. Copy the activity ID and use the IATI API Interface to find the data in that activity file.*
  4. For each of the data elements in the activity file check that they are correctly pulled through in the datasheet.
  5. Use the AidView Testing spreadsheet to check the new data elements and functionality.
  6. Mark off each of the columns in the spreadsheet as you check the funder's file.
  7. When checking the data elements note that not all funders publish to every data element. Use the Who is publishing? tool to check this.
  8. If you are unsure about whether the data is being produced correctly in the file check it against the IATI Activity Standard documentation
  9. Errors should be raised with data providers through David C's tracker or with White October through the Issue log in GitHub

In addition to the above there are some sample user journeys which have been created. They were originally used to test the data coming from the eXist backend datastore, but they can form the basis for some testing of the AidView web application as well.

Follow each user journey and check that the behaviour you see

  • is as you expected
  • doesn't create any errors
  • produces data which matches that coming from the API*

Again, errors should be raised with data providers through David C's tracker or with White October through the Issue log in GitHub

*Paste the Activity ID into the field marked "ID" and make sure that you select "full" in the Results row - all other fields can be left blank/default.

Clone this wiki locally