THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Identify and separate out failing integration tests that should be in unit test cases. (Aleks)
- Convert a few existing integration tests to unit tests as examples
- Define the expected code coverage we'd want at a functional module leve (i.e. module should have at least 80% unit testing coverage)
- Let's think about how we improve our existing integration tests (see https://issues.apache.org/jira/browse/FINERACT-949) and what's balance we want between integration tests and unit tests.
- Identify which unit test cases to focus on and ultimately have a wiki page with five categories, each category having 100 to 200 test cases and red or green tick mark to show if we have coverage.
- Near-term step to having this page is for individuals like Nayan and Istvan based on the test cases their teams have implemented to input into a Google Sheet at least the categories and ideally the test cases that were implemented so these can be focused on.
- Can reference previous test case documentation at https://drive.google.com/drive/folders/1T5MlVh0KWC6bQmqiZwEmoI73Q-0cuaxr?usp=sharing
- Create a test data set (No owner yet)
- Create a replicable cookbook for creation of test cases using DBUnit for setting up the data base and providing a few examples for others to follow. Test cases can be set up with simple CSV files.
- In future can use generate Jacoco and other reports for test coverage.
...
- 2020 Discussion Thread on Functional Test Cases and Creation of Postman Collections - https://markmail.org/thread/unn6rnwypqu5fgpi
- Fineract Issues on Improving Integration Tests
Action items
- H