import the Step Preconditions from Teststand to Requirements Gateway

[StephanG]

I want to import the Step Preconditions from a Teststand step to the Requirementsgateway. I tried this in the same way as the Step Comment is imported but it didn't work. How must I configure the NIRG project to realize this import?

regards,

Stephan

[AllenP]

Stephan,

This is not possible.

Allen P.
NI

[Santiago D]

Stephan,

Thank you for your interest in NI Requirements Gateway.  Could you please tell me more about how you would like to import the Step Precondition and why?

By default the NI Requirements Gateway TestStand type does not support this feature.  Customizing NI Requirements Gateway types can be challenging, and that's why I am wondering why you would like to the add the Step Precondition.  There might be a way of getting this information into NI Requirements Gateway in another way that does not require customization.

I am looking forward to your response,

Santiago D

[AllenP]

Unfortunately, the intermediate file generated by NIRG does not export this information, so customizing the types wouldn't help you.  The intermediate files are part of NIRG, so they cannot be customized.

I will pass this suggestion to R&D for future versions of the product.

Allen P.
NI

Message Edited by AllenP on 12-12-2006 10:50 AM

[Santiago D]

Allen is right.  I believed the TestStand type could be changed to add this property, but as Allen said, the intermediate file that is generate based on the TestStand Sequence does not contain this information, and this information can't be customized.

Why are you trying to add this information into NI Requirements Gateway?  I am wondering if there is another way to achieve your goal with the existing functionality in NI Requirements Gateway.

Santiago D

[StephanG]

When I export the Teststand sequence file to DOORS I want to have the precondition and the 'testprocedure' in one line. That shall result in a DOORS testdocument with the following appearance:

Precondition;  Testprocedure(= Teststand Description);   Expected Result (= Teststand Comment)

-> that means to have for every of this 3 items (Precondition, Testprocedure, Expected Result) an own attribute in the DOORS formal module.

At the moment the only solution I found is to create an own line for the Precondition and write it as the comment of a LABEL step type. But thats not very comfortable to read ...

Stephan G

[Santiago D]

Stephan,

Because NI Requirements Gateway does not bring a Step's precondition into the intermediate file, we won't be able to add the precondition directly.  On the other hand, the other option you have is to copy the precondition information into the Step comment which will be exported into the DOORS module.  This process could be automated by writing a script that communicates with TestStand API and copies the precondition to the step comment.

This process is a workaround and might become burdensome, especially if you have a large number of sequences.  Could you tell me a little more about the size and number of your TestStand sequences as well as what application you are working on?  In that way I could see if there is another way of implementing a solution that would be more beneficial.

Regards,

Santiago D