Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop QMTest test cases for CORE tickets resolved for 2.0.4 [QA160] #171

Closed
firebird-automations opened this issue Dec 29, 2007 · 2 comments

Comments

@firebird-automations
Copy link

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.

@firebird-automations
Copy link
Author

Modified by: @pmakowski

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

assignee: Philippe Makowski [ makowski ]

@firebird-automations
Copy link
Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant