Differences

This shows you the differences between two versions of the page.

dev:qa_testlink [2007/03/15 01:02]
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.org). +TestLink is a software testing and execution tracking system. More importantly it is an Opensource software given under the GPL license(http://testlink.org). 
-In order to maintain a premium quality ,Sahana is being using this facility for a long time.+In order to maintain a premium quality, Sahana has been using this facility for a long time. 
 + 
 +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 TestLink contains various test cases for different modules and other main areas(eg: Installer). +Currently TestLink contains various test cases for different modules and other main areas (eg: Installer). 
-Anyone can test available test cases after log in to http://test.sahana.lk/ which is Sahana's TestLink page.+Anyone can test available test cases after logging in to http://test.sahana.lk/ which is Sahana's TestLink page.
-To run a particular test case you have to click the "execute" button listed at top menue bar.after execution page appears you have to select the test case from the tree.+To run a particular test case you have to click the "execute" button listed at top menu bar. After execution page appears you have to select the test case from the tree.
{{dev:menue.png|}} {{dev:menue.png|}}
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 "Pass" or "Failed" by ticking the respective check box+  * After testing it a few times you have to mention the result as "Pass" or "Failed" by ticking the respective check box
  * 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" button   * Finally you can save the reults by clicking "Save Results" button
-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,Keywords,Results and the Build+there are several filters to filter results by Owner, Keywords, Results and the Build
{{dev:filter.png|}} {{dev:filter.png|}}
 +
Line 49: Line 52:
-You can jump to results page by clicking "Results" button at the top menu bar. +You can jump to the results page by clicking "Results" button at the top menu bar. 
-Using this feature we can obtain reports for overall test results,passed test cases,failed cases and many more.+Using this feature we can obtain reports for overall test results, passed test cases, failed cases and many more.
  * "General Test Suite Metrics" and "The Overall Build Status" will provide an overall result with percentage of success and failure.   * "General Test Suite Metrics" and "The Overall Build Status" will provide an overall result with percentage of success and failure.
-  * Blocked test cases and Failed Test cases can be listed seperately.+  * 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.   * By clicking "Total Bugs For Each Test Case" we can derive a report having available bugs for each test case.
-More interestingly this provide the feature to export a test report as a spreadsheet document +More interestingly this provides 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" option+We can also send the test report by mail using "send test report" option.
{{dev:reports.png|}} {{dev:reports.png|}}
 +
Line 67: Line 71:
-There are several sub categories under each module which contain test cases regarding to Functionality,Usability and +There are several sub-categories under each module which contain test cases regarding Functionality, Usability and
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" from the component panel appear in right side.+  * 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" from the component panel that appears on the right side.
     
-  * After giving a meaningful name and a summery you may create the category.+  * After giving a meaningful name and a summary, you may create the category.
-  * After creating the category you have to create a test case named "Functionality" if the test case addresses functional issues.otherwise "Usability" or "Accessibility".Naming conventions are to maintain the consistency.+  * After creating the category you have to create a test case named "Functionality" if the test case addresses functional issues. Otherwise "Usability" or "Accessibility". Naming conventions are to maintain the consistency.
-  * 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:newcases.png|}} {{dev:newcases.png|}}
-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 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 "update".

Navigation
  • Navigate