Throughout implementing the prototypes, we’ve employed a number of testing methodologies to ensure that the product is of a high quality. In this post, we’ll discuss four methodologies we have used: regression testing, code modularity, code quality checking and code metric monitoring.
After each significant change was made to the code, the prototype would be compiled into an android app and run through a number of scenarios on a phone. The purpose of testing in this way was to make sure that any changes did not break features which previously worked.
We made a number of design decisions to ensure that the code would be modular and easily maintainable:
- Adopting the server-client architecture leads to a disconnect of the user and the database.
- Using object oriented languages leads to modular code. In particular, the use of RedBean ORM and Backbone.js led to separately defined models, making it easily maintainable.
Code quality checking
Code metric monitoring
|Language||Line count limit||Final line count|