This document provides instructions for uploading test cases from an Excel sheet into TestLink. It explains that the Excel sheet should be saved as an XML file and then imported into TestLink. It highlights some key points such as including a step number for each test case and using valid codes for fields like execution type and importance. Special characters added between steps need to be replaced with XML tags to display each step on a new line in TestLink.
This document provides instructions for uploading test cases from an Excel sheet into TestLink. It explains that the Excel sheet should be saved as an XML file and then imported into TestLink. It highlights some key points such as including a step number for each test case and using valid codes for fields like execution type and importance. Special characters added between steps need to be replaced with XML tags to display each step on a new line in TestLink.
This document provides instructions for uploading test cases from an Excel sheet into TestLink. It explains that the Excel sheet should be saved as an XML file and then imported into TestLink. It highlights some key points such as including a step number for each test case and using valid codes for fields like execution type and importance. Special characters added between steps need to be replaced with XML tags to display each step on a new line in TestLink.
This document provides instructions for uploading test cases from an Excel sheet into TestLink. It explains that the Excel sheet should be saved as an XML file and then imported into TestLink. It highlights some key points such as including a step number for each test case and using valid codes for fields like execution type and importance. Special characters added between steps need to be replaced with XML tags to display each step on a new line in TestLink.
Download as XLSX, PDF, TXT or read online from Scribd
Download as xlsx, pdf, or txt
You are on page 1of 4
name summary preconditions
Test Case Title in TestLink
Test Case Summary in TestLink Test Case Pre- Conditions in TestLink Specify a Black Listed Route - using updateZoneLevelParameters API with blacklistedRoutes parameter Specify multiple different Black Listed Routes - using updateZoneLevelParameters API with blacklistedRoutes parameter Verify the Invalidity of the specified Black Listed Route's CIDR format Verify the Invalidity of Specified Multiple Black Listed Routes' CIDR format. Verify that a Black listed Static Route is not allowed to be created on the Private Gateway. Verify the Validity of black listing a sub-network of a black listed network Verify the Validity of black listing a Network when multiple black list networks are specified Verify the Invalidity of black listing a Network on a VPC VR belonging to a different Zone that doesnt black list that network Verify the Black Listed Route entires of a Zone in the "data_center_details" table after provision of Black listed Route CIDRs Verify the Black Listed Route entires of a Zone in the "data_center_details" table after deletion of Black listed Route CIDRs Creation of a Static Route whose CIDR was Black Listed on the Zone before deleting the black listed route from the Zone. Black List a Route that is already specified as a Static Route that allows access to the CIDR on a VPC VR- using updateZoneLevelParameters API with blacklistedRoutes parameter Verify that Administrators of the ROOT Domain can Black List Routes Verify that only Administrators of the ROOT Domain can Black List Routes Using updateZoneLevelParameters API with blacklistedRoutes parameter should Fail execution_type importance step_number actions expectedresults Test Case Execution Type in Test Link (1- Manual, 2- Automated) Test Case Importance in Test Link (3-High, 2- Medium, 1-Low) Test Case Step Number in Test Link Test Case Step Actions in Test Link. 1. Action One 2. Action Two Test Case Step Expected Results in Test Link execution_type2 name3 notes Test Case Step Execution Type in Test Link (1-Manual, 2-Automated) Test Case Keyword in Test Link (Specify your own if you want) Test Case Keyword notes in Test Link Steps to Use the Excel Sheet to upload the TestCases into TestLink: **Since there is currently no known procedure to directly upload an Excel sheet into the TestLink to import the test cases, I and Sangeetha came up with this procedure to convert an Excel sheet to the corresponding XML sheet which can be imported into the TestLink. 1. You may start documenting your testcases from Row 2 in Sheet 1. Continue entering test cases without leaving any row gaps in the sheet. If you leave row gaps, the data after the first row gap wont be present in the XML data sheet generated from this Excel Sheet. 2. Once the Test Cases are documented in the sheet1, save the document as a "XML Data" File ***. 3. Import the Test Cases onto Test link using the procedure to import TestCases using an XML Data File. ***I suggest saving the file as an Excel sheet before saving the same sheet as an XML Data File. Because saving the Excel sheet as an XML Data File will lead to lose of Data that do not use the XML Schema. Incase if you have mentioned any important details that you do not want to lose, its better to save an Excel Sheet copy before saving the same Excel sheet as an XML Data File with a different File name. Points to Remember: 1. Please note that not all column data needs to be provided for a given Test Case. But there are certain values that Test Link expects to see in the XML Data. One of such columns is the "TestCase Step Number". We tried to add a TestCase without the TestCase Step Number and TestLink refused to accept the TestCase. Hence you may specify any number in that cell. Logically, "1" makes sense to be provided as Step Number. 2 TestLink accepts importing of testcases when certain useful values are not specified. But you will see exception Information provided on the testcase registered on Test Link, when the appropriate data is not passed in a particular cell. For Example: Execution Type is registered as "Execution type : Unknown execution type code: 4 " when I passed "4" as the value in the Execution Type cell. The acceptable values are "1" for "Manual" and "2" for "Automated". Hence, keep an eye on such invalid entries. Similarly, Valid Values for Importance cell are "3" for High, "2" for Medium, "1" for Low. 3. You cannot create multiple Steps using Excel sheet. Hence specify All the steps of a test case in a single cell in the "actions" column. After entering each step, click on ALT + Enter to move to the next line in the same cell to specify the next step. 4. After entering all the steps in a Test Case, before planning to save the document as an XML Data document, Please use the procedure mentioned at http://howtouseexcel.net/how-to-remove-line-breaks-and-carriage- returns-in-cells-in-excel to replace the newlines with XML break tags. NOTE: Please pay special attention to Step 2 mentioned in the link. Use <br /> in Step 3 mentioned in the link to replace the new line character with <br />. 5. If you do not execute the above step, all the steps of the TestCase will be mentioned in a single link on TestLink. It will be difficult for the reader to comprehend the Information presented in a single line format. 6. This Excel sheet is generated using the XSD created from an Exported TestCase from TestLink. Hence keep in mind that the column names are the XML tags of Test Case identified by Test Link.