This is high because we need to make progress on automated testing or else it will never get done and we'll continue to find issues manually.
Now that InfoMapper applications are being deployed to implement complex websites, it is more challenging to detect when a software, configuration, or data problem is occurring on a deployed website. For example, recently the markdown conversion was not working well (which impacted many information popups) and time series graphing had a problem with absolute/relative paths (which broke all time series graphs). It would be helpful to be able to run automated tests on deployed websites to ensure that there are no fundamental issues. It probably does not make sense to implement a lot of tests for each website, but hopefully some basic tests could be implemented. The following are considerations:
Can automated testing be implemented in a general way without a lot of software developer skills? Is it a typical Angular development environment?
How can tests be written for a deployed website?
How are tests maintained in a repository?
Can the same tests or variants be easily used with multiple websites?
Can we automate the tests so that we have a way of monitoring deployed websites? The main issue is probably to run sufficient tests on a "version" release before deploying to "latest". Once latest is deployed, it can also be tested just to make sure things are working.
This is high because we need to make progress on automated testing or else it will never get done and we'll continue to find issues manually.
Now that InfoMapper applications are being deployed to implement complex websites, it is more challenging to detect when a software, configuration, or data problem is occurring on a deployed website. For example, recently the markdown conversion was not working well (which impacted many information popups) and time series graphing had a problem with absolute/relative paths (which broke all time series graphs). It would be helpful to be able to run automated tests on deployed websites to ensure that there are no fundamental issues. It probably does not make sense to implement a lot of tests for each website, but hopefully some basic tests could be implemented. The following are considerations: