Automatic Test Specification Creation by betelgeuse

[satelliteqe]

Automatic Test Specification Creation by betelgeuse

[elyezer]

@amsharma3 do you map each RFE/feature as being a Requirement?

I am looking for a way to identify what are the test cases related to an RFE so Betelgeuse can create that for you.

[amsharma3]

@elyezer That is true, we map each RFE as a Requirement.
The workflow is like this (which we follow) -

1. Release Plan
2. Requirement Document - (which will have all the RFEs mapped to it as work items)
3. Test Specification Document for each RFE (feature) - which will have all the test cases mapped to it as work items
4. Then Test run

[elyezer]

Talked with @amsharma3 and we came up with this RST file format for the Test Specification document:

:title:
:id:
:link: 

Title 1
=======

Paragraph 1

Paragraph 2

Sub Title
---------

Paragraph 1

Test Cases
==========

# Linking from a python module or package

.. link-python: tests.my_feature

# Link using test case field values

.. link-test-case: id=<someid>

.. link-test-case: feature=<some feature>

.. link-test-case: <field>=<field_value>

[elyezer]

Betelgeuse dropped pylarion dependency and only generates XML files to the importers. Since we don't have an importer to help creating the test specification we can close this issue.

In case we happen to have the test specification importer in the future we can either reopen this issue or create a new one.