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/16 09:26]
fran formatting/English
dev:qa_testlink [2009/07/06 20:36] (current)
Line 31: Line 31:
 To do that you have to select a module from the tree and all test cases will display on the right hand side. 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. Then you can run selected test cases, or all, and finally save the result.
 +
  
  
Line 38: Line 39:
  
  
-You can use filter to select only required test cases(eg :test cases those are not run).+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+there are several filters to filter results by Owner, Keywords, Results and the Build
  
 {{dev:filter.png|}} {{dev:filter.png|}}
 +
  
  
Line 50: 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 68: 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 addressedyou 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 testyou just have to add the test under summary and list steps and expected result. After that click "update".
  
  

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