Opensource Quality Assuarance Process

Tilli’s Quality Assurance Process comprises 8 major steps.

1. Product Development

   The Development team of Tilli will, first, develop the application as per the requirements and feedback from the community.

2. Product Release

   After the development is completed, the applications will be released and will also be updated in the repositories of Tilli.

3. User testing

   Product testing will be conducted. For Unit Testing, Jest is used to ensure the correctness of the codebase. Similarly, Manual User Acceptance Testing has been conducted. The Users and Developers are encouraged to test the application to detect bugs and issues. Coveralls is being used to test the code coverage.

4. Bugs Detection

   From the User Testing, Unit Testing, and UAT, Bugs will be detected. Moreover, we encourage our users to get involved in identifying the bugs.

5. Bugs Reporting

   The users and developers can update any issues/ bugs in our Tilli Issue Board. Developers needs to report the bugs/ issue as per the labels. Here is the list of available labels on our project board. In case you want to propose a new feature or you have any questions, feel free to create a new issue in the respective template.

6. Bugs Verification

   With the help of our users, developers, and contributor from around the globe, numerous bugs reported, enlisted in Tilli Issue Board, will be verified by the team of Tilli.

7. Verified Bugs Collection

   After validating the bugs with different parameters, verified bugs will be enlisted for the fixes.

8. Bug fixes

   The development team along with the contributors will work on fixing the bugs. After the fixes, The product will be released. For the releases, you can go to the Tilli Release Note.

   In this way, the iteration of this QA process will continue in Tilli.