Re: [Testlink-general] component/catagory/keyword
Test & requirements management
Brought to you by:
franciscom
|
From: Matthew W. <un...@id...> - 2004-10-12 21:23:09
|
Alan Jones said: > Hello, > I'm looking for some examples of how to use the component, > catagory and keyword fields. Component and Category are just ways to narrow down the list of tests- some common "components" of testing server software would be Security, Performance, and Stress Tests. Within the Security Component you might have tests confirming that line encryption works correctly, authentication works correctly, and authorization works correctly- that makes for a really good set of three Categories within that Component, and test cases are assigned to one of those Categories. Keywords are quite different- they provide cross-component ways of associating tests. For instance, rather than having a separate test plan for automated build tests (smoke/sniff tests performed on every nightly build, say), you might simply attach a keyword Smoke to some tests. Or perhaps you have a multiplatform product, and not all tests apply to all platforms- you could assign each platform a keyword, and assign each test keywords depending on which platforms it supports. For a web project, you might delineate which tests you want to be certain to run for every supported browser, and which tests you'd pass or fail based on a single browser. -- Matthew Weigel hacker un...@id... |