Testing Strategy
This project is an ongoing project. It is not fully deployable yet and so testing across our target number of user testers which is as diverse as possible (hence testing on large nuber of people with different backgrounds) hasn't occured yet.
We have however tested it across a smaller number of users that quite relatively diverse, to be able to determine which features to keep and which to update or even remove completley and this is how it went:
We placed the tester in an isolated location with no (or minimum) contact with the external world. The tester received a scenario to which he/she should act on, using the application. The scenario was :
You are working on a certain rail with no one in sight for the next 5 km. While trying to remove a faulty wire, you trip over and hit your head along the tracks. You assess your injury and determine that you are severely injured and incapable of moving. What do you do ?
We observed how the user interacted with the application, and observed the natural behaviour and insticts of where they would press first and how they interpreted what button would do what. We observed the natural flow of their response which extremely aided in our design and how we managed the UX of our product.
For the future, we plan to carry out these types of test on a larger scale of wider backgrounds. We would also like to cary out different kinds of tests to determine different sections of the product. We will also implemetn automated testing of the code written, and for all codes (functionalities) that will be written.