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/15 00:30] dinusha |
dev:qa_testlink [2009/07/06 20:36] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== What is TestLink ?===== | ===== What is TestLink ?===== | ||
| - | TestLink is a software testing and execution tracking system.More importantly it is an Opensource software given under the GPL license(http:// | + | TestLink is a software testing and execution tracking system. More importantly it is an Opensource software given under the GPL license(http:// |
| - | In order to maintain a premium quality , | + | In order to maintain a premium quality, Sahana |
| - | By using TestLink it is possible to create and maintain testcases, | + | 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 |
| + | ===== Executing a test case ===== | ||
| - | ===== How to add new test cases ?===== | + | Currently TestLink contains various |
| + | Anyone can test available test cases after logging in to http:// | ||
| - | currently TestLink contains various test cases for different modules and other main areas(eg: Installer). | ||
| - | Anyone can add new test cases after log in to http:// | ||
| - | There are several sub categories under each module which contain | + | To run a particular |
| - | Accessibility. | + | |
| - | Functionality test cases contain all tests regarding | + | |
| - | To add a new test case first you have to select a module(eg | + | {{dev:menue.png|}} |
| - | Then you have to expand that category and you can see available functional areas where tast cases have been prepared | + | |
| - | * If a new functional | + | * Then seperately test for that area according |
| - | + | ||
| - | * After giving a meaningful name and a summery you may create | + | |
| - | * After creating the category | + | * After testing it a few times you have to mention |
| - | * You have to provide | + | * If needed you can include additional information as a note |
| - | {{dev: | + | * Finally you can save the reults by clicking "Save Results" |
| - | If the functional area already listed and need to add a new test you just have to add the test under summery and list steps and expected result.after that click update | + | 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. | ||
| Line 39: | Line 36: | ||
| - | ===== Executing a test case ===== | + | ===== Using the Filter feature |
| - | To run a particular test case you have to click the " | ||
| - | {{dev:menue.png|}} | + | You can use a filter to select only required test cases (eg: test cases those are not run). |
| - | * Then seperately test for that area according | + | there are several filters |
| - | * After testing it few times you have to mention the result as " | + | {{dev: |
| - | * If needed you can include additional information as a note | ||
| - | * Finally you can save the reults by clicking "Save Results" | ||
| - | 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 tast cases would display in right hand side. | ||
| - | then you can run selected test cases or all and finally save the result | ||
| + | ===== Deriving Results ===== | ||
| + | You can jump to the results page by clicking " | ||
| + | Using this feature we can obtain reports for overall test results, passed test cases, failed cases and many more. | ||
| - | ===== Using the Filter feature ===== | + | * " |
| + | * Blocked test cases and Failed Test cases can be listed separately. | ||
| - | You can use filter to select only required | + | * By clicking "Total Bugs For Each Test Case" we can derive a report having available bugs for each test case. |
| - | there are several filters | + | More interestingly this provides the feature |
| + | We can also send the test report by mail using "send test report" | ||
| - | {{dev:filter.png|}} | + | {{dev:reports.png|}} |
| + | ===== How to add new test cases ?===== | ||
| - | ===== Deriving Results ===== | ||
| + | There are several sub-categories under each module which contain test cases regarding Functionality, | ||
| + | Accessibility. | ||
| + | Functionality test cases contain all tests regarding to that functional area, steps and expected results | ||
| - | You can jump to results page by clicking " | + | To add a new test case first you have to select a module (eg: Inventory Management System) |
| - | Using this feature we can obtain reports for overall test results, | + | 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 needs to be addressed, you have to click on the module name (eg: Inventory Management System) |
| + | |||
| + | * After giving a meaningful name and a summary, you may create the category. | ||
| - | * Blocked | + | * After creating the category you have to create a test case named " |
| - | * By clicking "Total Bugs For Each Test Case" we can derive | + | * You have to provide |
| + | |||
| + | {{dev: | ||
| + | |||
| + | If the functional area is already listed and you need to add a new test, you just have to add the test under summary and list steps and expected result. After that click " | ||
| - | More interestingly this provide the feature to export a test report as a spreadsheet document | ||
| - | And also we can send the test report by mail using "send test report" | ||
| - | {{dev: | ||
