This test setup allows testing of the controllers only. That is, the application logic that arranges the data used to create the UI. It does not allow for testing of the templates (which contain some presentational logic) or the integration testing of the controller and template layers together.
Our opinion is that following through with this, and establishing automated test coverage for the whole app, will take the dev team at least two weeks.
While it is certainly a good thing to be increasing automated test coverage, this will come at the cost of (1) not being able to work on anything else in the meantime, (2) becoming further entrenched in an app whose long-term maintenance has already been flagged as being problematic (TwinePlatform/twine-app#90).
With redesigns being talked of, the benefits of the above should be weighed against other development options.
We have looked into testing for the volunteer app, and setting up an initial test environment:
This test setup allows testing of the controllers only. That is, the application logic that arranges the data used to create the UI. It does not allow for testing of the templates (which contain some presentational logic) or the integration testing of the controller and template layers together.
Our opinion is that following through with this, and establishing automated test coverage for the whole app, will take the dev team at least two weeks.
While it is certainly a good thing to be increasing automated test coverage, this will come at the cost of (1) not being able to work on anything else in the meantime, (2) becoming further entrenched in an app whose long-term maintenance has already been flagged as being problematic (TwinePlatform/twine-app#90).
With redesigns being talked of, the benefits of the above should be weighed against other development options.