Test Plan

Our current test plan aims to test the most dynamic and important parts of our project, the content addition and filtered search. The template of our test plan mostly about these two topics. As the development process of this project continues the additional test scenarios for the other parts of the project will be included.
For the tracking of the tests we both use slack and github system. We will open a new section in our slack group to direct the test issues.
The github issues will be labeled with "testing" label. According to the result of the test, if there is no error found, the issue will be closed with a comment that explains the outcomes of the test. If the test finds a defect in the tested part of the system, then the issue will be further labeled with a label that explains the nature of the defect situation to the other team members, such as "question","duplicate","bug","invalid" or "wontfix" and a comment and will be added to explain the outcomes of the test throughly.

Test Case Document

You can find our current test case document through [here] (https://docs.google.com/spreadsheets/d/1Xo-3N4Yv_PkDz0gUkAaNR4VZZ4JHFqo0hd4lgvjXlJI/edit?usp=sharing).
You can find our previous test case document through here.