Hello, I have some dxl scripts for importing data from some csv test case results. What I do now is to prompt the user so I can get a number and then I create an attribute TestResult+Number entered by the user. Then I create a new view which also contains the number that the user has entered. In my company, normally this is performed creating a test run. As I see the both methods produce the same output, is there any difference from running the test and creating the attributes from dxl? Is there any command to create a test run from dxl? I have checked the documentation but I haven't found anything... Thank you, Best regards adrianro - Thu May 22 05:14:54 EDT 2014 |
Re: Run test from dxl Hello Actually there is no public test software for dxl at all. In our firm we have a small test framework and I have asked the person who has written it to publish it. But actually he has not done it until now. Best regards Wolfgang |
Re: Run test from dxl I'm not addressing your question, but I don't think that creating a new attribute for each test run is methodologically sound. 1000s of test runs means 1000s of new attributes, and you will need clever DXL to parse "Attribute Names" to determine the latest one. Instead, I think you want some kind of "test run" module, where each new row represents a new "Test Run", with its unique ID, and other information such as the RequirementID(s) tested. If you link this module to your Requirements you then write attr-DXL to find the "most recent" test run and display that informatin in the requirement module. Turns out I'm doing just about exactly that right now, except that we are capturing "Design Reviews" that include the requirement. -Louie |
Re: Run test from dxl I'm presently facing the same problem as adrianro. That is, using the built-in Tools-->Test Tracking menu from within a DOORS module, you can "Create Test Definition" and Create default attributes that will be used to create a new attribute for each "Test Run". Then, when a user chooses
|