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:24] fran formatting/English |
dev:qa_testlink [2009/07/06 20:36] (current) |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| By using TestLink it is possible to create and maintain testcases, store results by executing each test case and finally arrive at comprehensive test reports | By using TestLink it is possible to create and maintain testcases, store results by executing each test case and finally arrive at comprehensive test reports | ||
| + | |||
| Line 10: | Line 11: | ||
| ===== Executing a test case ===== | ===== Executing a test case ===== | ||
| - | currently | + | Currently |
| - | Anyone can test available test cases after log in to http:// | + | Anyone can test available test cases after logging |
| - | To run a particular test case you have to click the " | + | To run a particular test case you have to click the " |
| {{dev: | {{dev: | ||
| Line 20: | Line 21: | ||
| * Then seperately test for that area according to the specification and steps listed in the test case. | * Then seperately test for that area according to the specification and steps listed in the test case. | ||
| - | * After testing it few times you have to mention the result as " | + | * After testing it a few times you have to mention the result as " |
| * If needed you can include additional information as a note | * If needed you can include additional information as a note | ||
| Line 26: | Line 27: | ||
| * Finally you can save the reults by clicking "Save Results" | * Finally you can save the reults by clicking "Save Results" | ||
| - | You can execute all test cases available for a module in a single run | + | You can execute all test cases available for a module in a single run. |
| + | |||
| + | 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. | ||
| - | To do that you have to select a module from the tree and all tast cases would display in right hand side. | ||
| - | then you can run selected test cases or all and finally save the result | ||
| Line 37: | 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 49: | 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 67: | 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 |
