testlink用户手册英文(编辑修改稿)

testlink用户手册英文(编辑修改稿)内容摘要：

verview Products are the cornerstone of TestLink. Products are releases of your pany that may change their features and functionality over time but for the most part remain the same. Creating new products Create a new product is admin right. You cannot create products with the same name. You can assign a color of backgroung to product for a better lucidity. Things to note when creating a new product: Deleting Products themselves is not remended from the system, because the deletion of products would either orphan lots of test plan cases or lead to their deletion. Test Plans represent the testing of a product at a certain point of time. What this means is that All Test Plans are created from Product test cases. TestLink has the ability to import your data into a product. Data is read in CSVs form and is explained further in the import section. 7 Test Plans Creating a new Test Plan Test plans are the basis for test case execution. Test plans are made up of test cases imported from products at a specific point of time. Test plans can only be created by leads. Test plans may be created from other test plans. This allows users to create test plans from test cases that at a desired point in time. This may be necessary when creating a test plan for a patch. In order for a user to see a test plan they must have the propper rights. Rights may be assigned (by leads) in the define User/Project Rights section. This is an important thing to remember when users tell you they can39。 t see the project they are working on Builds Builds are a specific release of software. Each project in a pany is most likely made up of many different builds. In TestLink execution is made up of both builds and test cases. If there are no builds created for a project the execution screen will not allow you to execute. The metrics screen will also be pletely blank. Builds currently cannot be edited or deleted. Deleting TestPlans Test plans may be deleted from the main page by users with lead permissions. Deleting test plans permanently erases the test plan and all of its corresponding data (test cases, results, etc). The deleting of data is a scary prospect and should be reserved to extreme cases. TestLink also allows users to deactivate test plans so that they no longer appear as a menu option. 8 Test Case Suite Adding new Test Cases Test Case Suite is set of test cases which are defined to be run within Test Plan. Test case Suite is created via Add Test Cases from Test Specification to Test Plan. Test cases are added including Steps and Expected result. So, you must use 39。 Update modified Test Cases39。 page to update test scenario (version of test case). Data from multiple products can be added into one test plan. Test Specification data can be filtered by keywords (adjusted in navigation pane). Once data has been imported into a test plan it will be marked with checkmark. If a test case has already been imported it will be ignored if it is imported again. Removing Test Cases from Test Case Suite Test cases, categories, and ponents may be deleted from a test plan by users with Leader permissions from the Remove test cases page. Deleting data may be useful when first creating a test plan since there are no results. However, Deleting test cases will cause the loss of all results associated with them. Therefore, extreme caution is remended when using this functionality. Priority TestLink gives users with Leader rights the ability to assign ownership and priority to test cases. General Risk/Ownership is done at the category level. TestLink currently does not allow users to assign risk or ownership at the individual test case level. Risk levels are low, medium, high and Importance levels are 3, 2, 1. Users can rank the binations of risk and importance (L1, L2, L3, M1, H2, M3, H1, H2, H3) as priority A,B,C. Assigning risk, importance, ownership, and priority are all optional and will default to priority B in the metrics screen. Ownership Ownership affects both the execution and metrics screens. In the execution screen users have the ability to sort the executable test cases by the ones they have ownership of. In the main metrics screen there is a table that shows the remaining test cases by ownership. If there are no test case owners it defaults to none. A Tester can also see a metrics of own executed tests in main page if these metrics are enabled (see Installation manual). 9 Test Execution General Test execution is available when: Test Specification is written. Test Plan is created. Case Suite (for the Test Plan) is defined. Build is created. Test plan is assigned to testers (otherwise they cannot navigate to this Test Plan). Select a required Test Plan in main page and navigate to the 39。 Execute tests39。 link. Left pane serves for navigation in Test Case Suite via tree menu, filtering and define a tested build. Navigation The navigation pane consists from a 39。 Filter amp。 Settings39。 box and a tree menu with Test Case Suite. Filtering Test Cases This table allows the user to filter test cases for smart navigation before they are executed. .Owner: Users can filter test cases by their owner. Ownership is determined at the category level, is determined by leads, and can be changed at the Assign Risk and Ownership page under metrics. Keyword: Users can filter test cases by keyword. Keyw。