Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dev:qa_testlink [2007/03/14 23:34]
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
  
  
  
-===== How to add new test cases ?===== 
  
-currently TestLink contains various test cases for different modules and other main areas(eg: Installer). +===== Executing a test case =====
-Anyone can add new test cases after log in to http://test.sahana.lk/ which is Sahana's TestLink page.+
  
-There are several sub categories under each module which contain test cases regarding to Functionality,Usability and  +Currently TestLink contains various test cases for different modules and other main areas (eg: Installer)
-Accessibility+Anyone can test available test cases after logging in to http://test.sahana.lk/ which is Sahana's TestLink page.
-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 tast cases have been prepared 
  
-  * If new functional area need to be addressed you have to click on the module name(eg :Inventory Management System) and clik "New Categoryfrom the component panel appear in right side. +To run particular test case you have to click the "executebutton listed at top menu bar. After execution page appears you have to select the test case from the tree.
-   +
-  * After giving a meaningful name and a summery 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.+{{dev:menue.png|}}
  
-  * You have to provide a summery,steps and expected results for a particular test case.+  * Then seperately test for that area according to the specification and steps listed in the test case.
  
 +  * After testing it a few times you have to mention the result as "Pass" or "Failed" by ticking the respective check box
  
-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 you can include additional information as a note
  
 +  * 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.
  
 +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 "execute" button listed at top menue bar.after execution page appears you have to select the test case from the tree. 
  
-  * 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 "Pass" or "Failed" by ticking the respective check box 
  
-  * If needed you can include additional information as note+You can use filter to select only required test cases (eg: test cases those are not run).
  
-  * Finally you can save the reults by clicking "Save Results" button +there are several filters to filter results by Owner, Keywords, Results and the Build
  
-You can execute all test cases available for a module in a single run+{{dev:filter.png|}}
  
-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 to filter results by Owner,Keywords,Results and the Build+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 resultspassed test casesfailed cases and many more.
  
 +  * "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 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" option.
  
-===== Deriving Results =====+{{dev:reports.png|}}
  
  
-You can jump to 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. 
  
-  * "General Test Suite Metrics" and "The Overall Build Status" will provide an overall result with percentage of success and failure.+===== How to add new test cases ?=====
  
-  * Blocked test cases and Failed Test cases can be listed seperately. 
  
-  By clicking "Total Bugs For Each Test Casewe can derive report having available bugs for each test case.+There are several sub-categories under each module which contain test cases regarding Functionality, Usability and  
 +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. 
 + 
 +  If a new functional area needs to be addressed, you have to click on the module name (eg: Inventory Management System) and click "New Categoryfrom the component panel that appears on the right side. 
 +   
 +  * After giving 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. 
 + 
 +  * You have to provide a summary, steps and expected results for a particular test case. 
 + 
 +{{dev:newcases.png|}}
  
-More interestingly this provide the feature to export a test report as a spreadsheet document +If the functional area is already listed and you need to add new test, you just have to add the test under summary and list steps and expected result. After that click "update".
-And also we can send the test report by mail using "send test reportoption+
  
  

Navigation
QR Code
QR Code dev:qa_testlink (generated for current page)