Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dev:qa_testlink [2007/03/16 09:26] fran formatting/English |
dev:qa_testlink [2009/07/06 20:36] (current) |
||
---|---|---|---|
Line 31: | Line 31: | ||
To do that you have to select a module from the tree and all test cases will display on the right hand side. | To do that you have to select a module from the tree and all test cases will display on the right hand side. | ||
Then you can run selected test cases, or all, and finally save the result. | Then you can run selected test cases, or all, and finally save the result. | ||
+ | |||
Line 38: | Line 39: | ||
- | You can use filter to select only required test cases(eg :test cases those are not run). | + | You can use a filter to select only required test cases (eg: test cases those are not run). |
- | there are several filters to filter results by Owner, | + | there are several filters to filter results by Owner, Keywords, Results and the Build |
{{dev: | {{dev: | ||
+ | |||
Line 50: | Line 52: | ||
- | You can jump to results page by clicking " | + | You can jump to the results page by clicking " |
- | Using this feature we can obtain reports for overall test results, | + | Using this feature we can obtain reports for overall test results, passed test cases, failed cases and many more. |
* " | * " | ||
- | * Blocked test cases and Failed Test cases can be listed | + | * Blocked test cases and Failed Test cases can be listed |
* By clicking "Total Bugs For Each Test Case" we can derive a report having available bugs for each test case. | * By clicking "Total Bugs For Each Test Case" we can derive a report having available bugs for each test case. | ||
- | More interestingly this provide | + | More interestingly this provides |
- | And also we can send the test report by mail using "send test report" | + | We can also send the test report by mail using "send test report" |
{{dev: | {{dev: | ||
+ | |||
Line 68: | Line 71: | ||
- | There are several sub categories under each module which contain test cases regarding | + | There are several sub-categories under each module which contain test cases regarding Functionality, |
Accessibility. | Accessibility. | ||
- | Functionality test cases contain all tests regarding to that functional area,steps and expected results | + | Functionality test cases contain all tests regarding to that functional area, steps and expected results |
- | To add a new test case first you have to select a module(eg :Inventory Management System) | + | To add a new test case first you have to select a module (eg: Inventory Management System) |
- | Then you have to expand that category and you can see available functional areas where tast cases have been prepared | + | Then you have to expand that category and you can see available functional areas where test cases have been prepared. |
- | * If a new functional area need to be addressed you have to click on the module name(eg :Inventory Management System) and clik "New Category" | + | * If a new functional area needs to be addressed, you have to click on the module name (eg: Inventory Management System) and click "New Category" |
| | ||
- | * After giving a meaningful name and a summery | + | * After giving a meaningful name and a summary, |
- | * After creating the category you have to create a test case named " | + | * After creating the category you have to create a test case named " |
- | * You have to provide a summery,steps and expected results for a particular test case. | + | * You have to provide a summary, steps and expected results for a particular test case. |
{{dev: | {{dev: | ||
- | If the functional area already listed and need to add a new test you just have to add the test under summery | + | If the functional area is already listed and you need to add a new test, you just have to add the test under summary |