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/14 23:25] mahesh |
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 |
- | ===== How to add new test cases ?===== | ||
- | currently TestLink contains various | + | ===== Executing a test case ===== |
- | Anyone can add new test cases after log in to http:// | + | |
- | There are several sub categories under each module which contain | + | Currently TestLink contains various |
- | Accessibility. | + | Anyone can test available |
- | Functionality | + | |
- | 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 | ||
- | * If a new functional area need to be addressed | + | To run a particular test case you have to click the "execute" |
- | + | ||
- | * After giving a meaningful name and a summery | + | |
- | * After creating the category you have to create a test case named " | + | {{dev:menue.png|}} |
- | * You have to provide a summery, | + | * Then seperately test for that area according |
+ | * After testing it a few times you have to mention the result as " | ||
- | 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 | + | * If needed |
+ | * 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 test cases will display on the right hand side. | ||
+ | Then you can run selected test cases, or all, and finally save the result. | ||
- | ===== Executing a test case ===== | ||
- | To run a particular test case you have to click the " | ||
- | * Then seperately test for that area according to the specification and steps listed in the test case. | + | ===== Using the Filter feature ===== |
- | * After testing it few times you have to mention the result as " | ||
- | * If needed you can include additional information as a note | + | You can use a filter to select only required test cases (eg: test cases those are not run). |
- | * Finally you can save the reults | + | there are several filters to filter results |
- | You can execute all test cases available for a module in a single run | + | {{dev: |
- | 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 | ||
- | ===== Using the Filter feature ===== | ||
+ | ===== Deriving Results ===== | ||
- | You can use filter to select only required test cases(eg :test cases those are not run). | ||
- | there are several filters | + | You can jump to the 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 separately. | ||
+ | * By clicking "Total Bugs For Each Test Case" we can derive a report having available bugs for each test case. | ||
+ | More interestingly this provides the feature to export a test report as a spreadsheet document. | ||
+ | We can also send the test report by mail using "send test report" | ||
- | ===== Deriving Results ===== | + | {{dev: |
- | You can jump to results page by clicking " | ||
- | Using this feature we can obtain reports for overall test results, | ||
- | * " | + | ===== How to add new test cases ?===== |
- | * Blocked test cases and Failed Test cases can be listed seperately. | ||
- | | + | 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 | ||
+ | |||
+ | 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 test cases have been prepared. | ||
+ | |||
+ | | ||
+ | |||
+ | * After giving | ||
+ | |||
+ | * After creating the category you have to create a test case named " | ||
+ | |||
+ | * You have to provide a summary, steps and expected results | ||
+ | |||
+ | {{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" | ||