You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Test filename must adhere to template: <project-code>_<bug-no>.qmt (for example: core_357.qmt)
2. All test for bugs should go into firebird\qa\trunk\testsuite\bugs.qms directory in SourceForge SVN repository.
3. See http://www.firebirdsql.org/index.php?op=devel&sub=qa for instrutions how to design and implement new test.
4. Pick bug you want to develop tests for and make a SUB-TASK to this issue. Please, develop tests for fixed bugs first, to extend our database of regression tests.
5. Please commit tests to the SVN repository one at a time, and log BUG ID AND SUB-TASK ID in the commit comment, so the test case would be automatically linked to the JIRA tickets.
6. Please, don't forget to log your time spent on the issue on RESOLUTION form ! Realistic estimate is enough (as you'll probably work on several tickets at once).
7. If you'll work on any issue for more than a day, don't forget to log you work progress.
The text was updated successfully, but these errors were encountered:
Submitted by: @pcisar
Assigned to: @pmakowski
Jira_subtask_outward QA161
Jira_subtask_outward QA162
Jira_subtask_outward QA163
Jira_subtask_outward QA164
Jira_subtask_outward QA165
Notes for test developers:
1. Test filename must adhere to template: <project-code>_<bug-no>.qmt (for example: core_357.qmt)
2. All test for bugs should go into firebird\qa\trunk\testsuite\bugs.qms directory in SourceForge SVN repository.
3. See http://www.firebirdsql.org/index.php?op=devel&sub=qa for instrutions how to design and implement new test.
4. Pick bug you want to develop tests for and make a SUB-TASK to this issue. Please, develop tests for fixed bugs first, to extend our database of regression tests.
5. Please commit tests to the SVN repository one at a time, and log BUG ID AND SUB-TASK ID in the commit comment, so the test case would be automatically linked to the JIRA tickets.
6. Please, don't forget to log your time spent on the issue on RESOLUTION form ! Realistic estimate is enough (as you'll probably work on several tickets at once).
7. If you'll work on any issue for more than a day, don't forget to log you work progress.
The text was updated successfully, but these errors were encountered: