From version 7.2, TFS4JIRA supports bi-directional synchronization of TFS / Azure DevOps (formerly VSTS) Test Steps. Test steps can be mapped to a JIRA text field when workitem type Test Case is mapped
How to map Test Steps
Please follow the following instruction in order to map Test Steps:
- Map Work Item Type Test Case to a Jira issue type
Map TFS field Steps to a Jira RichText type field
It's suggested to map Steps to a Jira custom RichText type field.
It's fine to map Description (Jira) with Steps (TFS), but you will not be able to synchronize Description (Jira) with any other fields in TFS because TFS4JIRA supports 1 to 1 mapping only for now.
How it works
In TFS / Azure DevOps (formerly VSTS) Test Case, Steps is structured and displayed as the screenshot below,
After the synchronization Steps will be reflected in a table with 4 columns (Step, Action, Expected result, Step id) in Jira,
- If you change the header of the table (Step, Action, Expected result, Step id) in Jira, it will erase the Steps in TFS / Azure DevOps (formerly VSTS) due to the failure of conversion.
- If the mapped Jira text field contains any content other than the table (Step, Action, Expected result, Step id), this content will be erased when TFS / Azure DevOps (formerly VSTS) → JIRA synchronization happens.
- If the mapped Jira text field contains a deformed table, an errors occur and synchronization for Test Steps will not be done:
Supported formats and limitations
|TFS||Jira||TFS → Jira||Jira → TFS|
4 columns table with headers (Step, Action, Expected result)
|n/a||Other text formats, images, icons, etc|
|n/a||Anything that is out of 4 columns table bound|
It is possible to include attachments in Test Case which related to any Test Step.
The relation to a particular Test Step is built by the Comments at the Attachment.
These attachments will be synchronized to Jira as regular attachments if the Attachment Synchronization Mode in the sync profile is ON. However, the relations between attachments and step will not be reflected in Jira after the synchronization.
For Jira → TFS / Azure DevOps (formerly VSTS), attachments will be synchronized without any relations to Test Steps.