Test link

54,793 views
54,659 views

Published on

Published in: Education
8 Comments
39 Likes
Statistics
Notes
No Downloads
Views
Total views
54,793
On SlideShare
0
From Embeds
0
Number of Embeds
3,578
Actions
Shares
0
Downloads
2,596
Comments
8
Likes
39
Embeds 0
No embeds

No notes for slide

Test link

  1. 1. TestLink – test management system
  2. 2. HOW TO WORK WITH TESTLINK <ul><li>Create a Project </li></ul><ul><li>Create Test Cases (Test Suites) for this Project </li></ul><ul><li>Create Test Plan </li></ul><ul><li>Specify Build of the Project you are going to test </li></ul><ul><li>Add Test Cases to the Test Plan </li></ul><ul><li>Assign Test Cases to Test Engineers </li></ul><ul><li>Execute Test Cases (Test Engineers) </li></ul><ul><li>See Reports and Charts </li></ul>
  3. 3. HOW TO WORK WITH TESTLINK <ul><li>Additional facilities: </li></ul><ul><li>Assigning Keywords (we may form a group of Test Cases for Regression tests) </li></ul><ul><li>Specifying Requirements (we may bind them with Test Cases in the many-to-many relation and see if our Test Cases cover our requirements) </li></ul><ul><li>Events log (you can see here the history of all the changes) </li></ul>
  4. 4. STEP 1. CREATE A PROJECT <ul><li>To create a project go to the Test Project Management section: </li></ul>
  5. 5. STEP 1. CREATE A PROJECT
  6. 6. STEP 1. CREATE A PROJECT. IMPORTANT FIELDS <ul><li>Name </li></ul><ul><li>ID (used for forming a unique Test Cases ID) </li></ul><ul><li>E.g. ET-03 means that the Test Case is created for Easy Test project and it has ID=3 </li></ul><ul><li>Project Description (what is the aim of the Project, what is the target group, what is the business logic, what is the Test Environment) </li></ul>
  7. 7. STEP 1. CREATE A PROJECT. IMPORTANT FIELDS <ul><li>Enhanced features: </li></ul><ul><li>Requirements feature – we may specify requirements and see if they are well-covered by Test Cases </li></ul><ul><li>Testing priority – we may assign priority to Test Cases (high, medium, low) </li></ul><ul><li>Test Automation – we may specify whether the test should be performed manually or automatically </li></ul><ul><li>Inventory – to tell the truth, I didn’t understand what it means </li></ul>
  8. 8. STEP 1. CREATE A PROJECT. IMPORTANT FIELDS <ul><li>You can now set this project here, like in Mantis, in the top right corner </li></ul>
  9. 9. STEP 2. CREATE TEST CASES
  10. 10. STEP 2. CREATE TEST CASES. CREATING TEST SUITE
  11. 11. STEP 2. CREATE TEST CASES. CREATING TEST SUITE
  12. 12. STEP 2. CREATE TEST CASES
  13. 13. STEP 2. CREATE TEST CASES <ul><li>Test Case Title </li></ul><ul><li>Summary </li></ul><ul><li>Preconditions </li></ul><ul><li>Execution type </li></ul><ul><li>(manual or automated) </li></ul><ul><li>Test importance </li></ul><ul><li>(High, Medium or Low) </li></ul>
  14. 14. STEP 2. CREATE TEST CASES
  15. 15. STEP 2. CREATE TEST CASES
  16. 16. STEP 2. CREATE TEST CASES <ul><li>We may also import & export Test Suites & Test Cases (in the .XML format): </li></ul><ul><li>We import them from one project </li></ul><ul><li>And export the file in other </li></ul><ul><li>Unfortunately, now it’s the only way to transfer them from one project to another </li></ul>
  17. 17. STEP 3.SPECIFY TEST PLAN <ul><li>TestLink won’t allow you to execute Test Suites if you don’t create a Test Plan and specify Test Build. </li></ul><ul><li>How to do that? Elementary my dear Watson! </li></ul><ul><li>Let’s begin from the Plan </li></ul>
  18. 18. STEP 3.SPECIFY TEST PLAN
  19. 19. STEP 3. SPECIFY TEST PLAN <ul><li>Current Test Plan will appear in the top right corner </li></ul>
  20. 20. STEP 4. SPECIFY BUILD <ul><li>After you’ve added a Test Plan menu for adding Test Build appears: </li></ul><ul><li>Add a new build there </li></ul>
  21. 21. STEP 4. SPECIFY BUILD
  22. 22. STEP 5. ADD TEST CASES TO THE PLAN <ul><li>Unfortunately, only Test Cases, not Test Suites or the whole Test Specification can be added to a Test plan. So, until you don’t select one separate TC the button “Add to Test Plans” will not appear. </li></ul>
  23. 23. STEP 5. ADD TEST CASES TO THE PLAN <ul><li>Then you can choose what Test Plans you want to add the selected TC to. </li></ul>
  24. 24. STEP 6. ASSIGN TEST CASE EXECUTION TO TESTERS <ul><li>Before assigning TC to testers you should create a DB of users with appropriate roles here: </li></ul><ul><li>Or here: </li></ul>
  25. 25. STEP 6. ASSIGN TEST CASE EXECUTION TO TESTERS <ul><li>Add the users you need filling in the form: </li></ul>
  26. 26. STEP 6. ASSIGN TEST CASE EXECUTION TO TESTERS <ul><li>Then you can assign TC execution here: </li></ul>
  27. 27. STEP 6. ASSIGN TEST CASE EXECUTION TO TESTERS <ul><li>You can assign test cases to testers and send them email notifiactions: </li></ul>
  28. 28. STEP 7. EXECUTE TESTS <ul><li>To start executing tests Test Engineer should go to test Execution section: </li></ul><ul><li>Then choose a TC and you will face: </li></ul>
  29. 29. STEP 7. EXECUTE TESTS <ul><li>We may also connect TestLink with our bug-tracking system Mantis , then during execution you will see: </li></ul>
  30. 30. STEP 7. EXECUTE TESTS <ul><li>After click on </li></ul><ul><li>“ Create new bug”, </li></ul><ul><li>creating the bug </li></ul><ul><li>using Mantis </li></ul><ul><li>user interface </li></ul><ul><li>and reorganinzing </li></ul><ul><li>the windows . </li></ul>
  31. 31. STEP 7. EXECUTE TESTS <ul><li>Test engineer writes the issue ID on Testlink: </li></ul><ul><li>And it looks like here after saving: </li></ul>
  32. 32. STEP 7. EXECUTE TESTS <ul><li>Execution history is being saved: </li></ul>
  33. 33. STEP 8. SEE REPORTS AND CHARTS <ul><li>After test case execution is finished you may see the results of it using Test Reports section </li></ul><ul><li>Or here: </li></ul>
  34. 34. STEP 8. SEE REPORTS AND CHARTS <ul><li>You’ll face the following page: </li></ul>
  35. 35. STEP 8. SEE REPORTS AND CHARTS <ul><li>Test Plan Rerport - the document has options to define a content and a document structure. You may choose the info you wanna get </li></ul><ul><li>and you will surely get it! </li></ul>
  36. 36. STEP 8. SEE REPORTS AND CHARTS <ul><li>Test Plan report (part of it) </li></ul>
  37. 37. STEP 8. SEE REPORTS AND CHARTS <ul><li>The document 'Test Report' has options to define a content and document structure. It includes Test cases together with test results. </li></ul>
  38. 38. STEP 8. SEE REPORTS AND CHARTS <ul><li>Test result matrix </li></ul>
  39. 39. STEP 8. SEE REPORTS AND CHARTS <ul><li>Charts </li></ul>
  40. 40. STEP 8. SEE REPORTS AND CHARTS <ul><li>Charts – results by tester (there are only unassigned test cases in the diagram): </li></ul>
  41. 41. STEP 8. SEE REPORTS AND CHARTS <ul><li>Charts – Results for top level suites: </li></ul><ul><li>1. Log in the application </li></ul><ul><li>2. News module </li></ul>
  42. 42. STEP 8. SEE REPORTS AND CHARTS <ul><li>Blocked, Failed, and Not Run Test Case Reports </li></ul><ul><li>These reports show all of the currently blocked, failing, or not run test cases. </li></ul><ul><li>E.g. </li></ul>
  43. 43. STEP 8. SEE REPORTS AND CHARTS <ul><li>General Test Plan Metrics </li></ul><ul><li>This page shows you only the most current status of a Test plan by test suite, owner, and keyword. </li></ul>
  44. 44. STEP 8. SEE REPORTS AND CHARTS <ul><li>Query metrics – work like filters in Mantis </li></ul>
  45. 45. STEP 8. SEE REPORTS AND CHARTS <ul><li>Requirements based report </li></ul><ul><li>If we have some requirements specified and have connected them with TC we can see the following report: </li></ul>
  46. 46. ADDITIONAL FACILITIES. ASSIGNING KEYWORDS <ul><li>Go to the “Assign Keywords” section </li></ul><ul><li>Select some Test Suite and then you’ll be able o go to “Keywords Management” </li></ul>
  47. 47. ADDITIONAL FACILITIES. ASSIGNING KEYWORDS <ul><li>Add keywords if there are no KW at all or if there are no KW you need: </li></ul>
  48. 48. ADDITIONAL FACILITIES. ASSIGNING KEYWORDS <ul><li>Now you can add Keywords both to Test Suites & Test Cases, either all the Keywords (>>) or only one KW (>) </li></ul>
  49. 49. ADDITIONAL FACILITIES. ASSIGNING KEYWORDS <ul><li>Then you’ll be able to see such a useful chart demonstrating the Results by KW: </li></ul>
  50. 50. ADDITIONAL FACILITIES. SPECIFYING REQUIREMENTS <ul><li>You can open the section in this way: </li></ul><ul><li>Or in this: </li></ul>
  51. 51. ADDITIONAL FACILITIES. SPECIFYING REQUIREMENTS <ul><li>Requirements Specification adding </li></ul>
  52. 52. ADDITIONAL FACILITIES. SPECIFYING REQUIREMENTS <ul><li>Then we create Requirements: </li></ul>
  53. 53. ADDITIONAL FACILITIES. SPECIFYING REQUIREMENTS <ul><li>Then we create </li></ul><ul><li>Requirements: </li></ul>
  54. 54. ADDITIONAL FACILITIES. SPECIFYING REQUIREMENTS <ul><li>Pay attention that there are different types of the Requirements: </li></ul>
  55. 55. ADDITIONAL FACILITIES. SPECIFYING REQUIREMENTS <ul><li>Then assign requirements to Test Cases: </li></ul>
  56. 56. ADDITIONAL FACILITIES. SPECIFYING REQUIREMENTS <ul><li>Select Test Suite or Test Case and assign it to 1 or more requirements (R. can be assign to TC in the relation man-to-many) </li></ul>
  57. 57. ADDITIONAL FACILITIES. EVENTS LOG
  58. 58. WHAT BENEFITS DO WE HAVE? <ul><li>We have all the documentation structured and organized. </li></ul><ul><li>We solve the problem of version control. </li></ul><ul><li>We can control the testing process (Events log + different kinds of Reports) </li></ul><ul><li>We can see if all the requirements are covered with Test Cases </li></ul><ul><li>We can select Test Cases for Regression Testing </li></ul><ul><li>We can see the results of testing in a very clear and easy-to-use form. </li></ul><ul><li>etc. </li></ul>
  59. 59. SOURCES <ul><li>http://blog.testlink.org/ </li></ul><ul><li>http://testlink.org/demo/ </li></ul><ul><li>http://lib.custis.ru/TestLink#.D0.9D.D0.B0.D0.B7.D0.BD.D0.B0.D1.87.D0.B5.D0.BD.D0.B8.D0.B5_.D1.82.D0.B5.D1.81.D1.82.D0.BE.D0.B2_.D0.B4.D0.BB.D1.8F_.D0.BF.D1.80.D0.BE.D0.B3.D0.BE.D0.BD.D0.B0 </li></ul>
  60. 60. THANK YOU FOR YOUR ATTENTION!

×