35
edits
Julianharty (talk | contribs) (Added some initial goals. These are open to change. Others are also welcome.) |
Julianharty (talk | contribs) (Added Testing of Search.) |
||
Line 5: | Line 5: | ||
* Effective Logging: to improve testing and troubleshooting. Revise logging in the app to report relevant data that may help with diagnostics, particularly for recent problems including crashes, access to zim files, etc. | * Effective Logging: to improve testing and troubleshooting. Revise logging in the app to report relevant data that may help with diagnostics, particularly for recent problems including crashes, access to zim files, etc. | ||
* Better automated testing: to increase our confidence in the product and make the automated builds and testing more trustworthy and useful. This will include creating additional Mock Objects: Implement the mocks needed for tests that use network operations e.g. download tests. | * Better automated testing: to increase our confidence in the product and make the automated builds and testing more trustworthy and useful. This will include creating additional Mock Objects: Implement the mocks needed for tests that use network operations e.g. download tests. Also, be great to improve the testing of key functionality including searching and results. | ||
* Global Error Handling: Review the initial spike that includes a global error handler and triage whether to use it, do something similar instead, or not bother. | * Global Error Handling: Review the initial spike that includes a global error handler and triage whether to use it, do something similar instead, or not bother. | ||
* Better error detection and error handling in the app: so fewer problems / errors cause the app to crash in use. | * Better error detection and error handling in the app: so fewer problems / errors cause the app to crash in use. |
edits