ccallan
New Contributor
Joined 4 years ago
User Profile
User Widgets
Contributions
Test Automation task only uses file extension to determine validity of file contents
I have found a bug in the Test Automation task with Upload for the Test Automation Type Prerequisites: working JIRA project with Zephyr Squad active; junit file from a test automation output saved with a ".junit" file extension (valid xml inside) Steps To Repro: 1) Login to JIRA as a valid user for the project 2) Navigate to the Test Automation and Create a New Task 3) Setup the Task with "Upload" for the Automation Type and the ".junit" file selected as the input * other data is unimportant 4) Execute the Task Actual Results: Task will fail with the vague error, "Found invalid file format. Please provide valid file to import with respect to configured framework." Expected Results: Task should run without error since the internals of the file are valid xml (i.e. load the file into your parser to see if exceptions occur rather than assuming the file extension says anything about the file contents) Testing has shown that if you rename the ".junit" to ".xml" that the Task will execute without error. Apparently the file attaching on this site suffers from the same bug 🙂1.1KViews0likes0CommentsRe: Turn off wiki markup formatting in Test Details
I submitted an enhancement request for this https://community.smartbear.com/t5/Feature-Requests/Allow-configuration-for-wiki-text-renderer-for-Test-Steps/idi-p/224693#M789 I figure we can't be the only two customers that have a hyphen in their test steps. I've seen another variation on this where inventory ID values (e.g. 1234:P) was being displayed using emojis. Hopefully this gets some traction956Views0likes0CommentsAllow configuration for wiki/text renderer for Test Steps/Details
Currently, when you insert a URL (for example) that contains a "-" (e.g. https://mycompany.com/core/reg/by-binary-data) the shown text after saving the test is struckthrough. The Test Details/Step text box is hard-coded to only use the Wiki-style Renderer and so characters that are perfectly valid in URLs are interpreted as some manner of markup. Just allowing customers to modify the renderer used to the Text Renderer in these fields, like the other JIRA text fields on forms, would allow these characters to be shown as expected.1.4KViews3likes1CommentRe: Turn off wiki markup formatting in Test Details
I have the exact same issue with URLs that contain guids. Seems like this could be turned off if I knew what text field configuration it was using, all the other JIRA text fields allow you to apply a text renderer instead. Maybe you found a workaround?968Views0likes2Comments