To see this working, head to your live site.

Importing from already existing automated TCs

Hi!

We have just enabled trial version of AIO, and was wondering if we could import already existing automated test cases from repository we have. We have cypress-cucumber, playwright, and simple cypress test cases. Is there any best practice on which way I could import all the test cases (around 500~) into an AIO suite? Do I have to add it manually one-by-one?

Thanks, Cheers

6 answers0 replies

6 Comments

Commenting on this post isn't available anymore. Contact the site owner for more info.

Richárd Szanyi

Jul 30

Thanks!

I've added the proper requirement tags, that works fine after import.

However, my case key cannot be found even though I've added @JM-TC-1, etc. on the test cases I have in the feature file. AIO does not have any test case yet.

As you can see on this screenshot, my cypress reporter even tells me this:

Do I have to first import a .feature file so that case key gets assigned in AIO, and then do the tagging manually by checking AIO to feature file side-by-side? :(

Cheers!

Richárd Szanyi

Jul 29

Thank you Niharika for your prompt response!

I suppose if I setup reporter for our cypress cucumber framework, and report results into AIO - how the sync is happening when a cucumber test case is changed, and on what axis does it sync together?

e.x:

buttonTest.feature

Feature: Testing button functionality

Background: 
* I am logged in

Scenario: Button can be clicked
* I open the page containing the button
* I click on the button

I imported this as bdd test case, I already have it in AIO. This test case can be changed based on requirement change.

buttonTest.feature

Feature: Testing button functionality

Background: 
* I am logged in

Scenario: Button can be clicked
* I open the page containing the button
* Button should be visible
* I click on the button

How will that change take place in AIO? When I upload my cucumber json will it change the feature file according to that change? Will a new test case be created? I want to achieve the following, maybe you know the best way for me to approach it.

Upload all of the automated cucumber-cypress, cypress, playwright test cases into AIO.
Have them updated if change is happening to the actual test case such as above.
When we run our daily tests, I want the results to be inside AIO relating to the Jira.

They already have a tag on them associated by Jira IDs, however it is not @REQ-**** so I have to re-tag every cucumber case we have, do you know a way on how I can avoid it? Maybe let AIO know what tags we use, and what tags to sync?

Thanks!

Niharika

Jul 29

Replying to

Hello Richard,

For cucumber, updating steps is possible, since the cucumber.json report contains step details. If you upload the cucumber json, the import call has a flag - bddForceUpdateCase - setting to true, will update the steps if case exists in AIO (either recognized by case key eg. AT-TC-221 or by automation key which is setup in case created by AIO while importing results). For cases where no key or automation key is found, they would be created new. For TS based cases, since there are no Gherkin like steps and only code, only the status of the case can be updated.

To sum up:

Upload all of the automated cucumber-cypress, cypress, playwright test cases into AIO. Niharika : Can be done with varying degree of details using different methods as highlihted in the first response
Have them updated if change is happening to the actual test case such as above. Niharika : Supported for Gherkin BDD based frameworks. Not possible for TS based cases [ though APIs for creation/updation of cases are available, if you want to call them in your code]
When we run our daily tests, I want the results to be inside AIO relating to the Jira. Niharika : This is achievable for all frameworks either via APIs or supported reporters.

Hope that clarifies.

Regards, Niharika

Richárd Szanyi

Jul 29

Replying to

Thank you! Is there a possibility to map my already existing tags? As in I have a jira ticket with PP-1234, and an epic ABOE-4321 and the cucumber scenario has @PP-1234 as well as @ABOE-4321 on it respectively. Is it possible to map these somehow when I upload? Shall I just use it as automation key when importing feature file?

Niharika

Jul 29

Replying to

Hello Richard,

Unfortunately, the parser looks for the specific string @JREQ- to identify a Jira requirement. However, the requirement keys will be added to tags of the case created - if it helps to map it later. Automation key serves a very specific usecase, that of identifying a case, and it is not recommended to use same key in multiple cases, which would be a case for story or epic id.

Hope that helps.

Regards, Niharika

Niharika

Jul 29

Hello Richard,

Here's a summary of how cases can be created from automated cases in AIO

Cucumber feature files [Cypress-Cucumber] -
a. Feature files can be imported using the Import Feature files flow, wherein each scenario is created as a testcase with steps being reported as BDD steps in AIO. This can be done either via the UI flow or even via API
b. Another option to do the same is by using the report file, cucumber.json. While importing, users have an option to set createNewCase as true and cases will be created from the report file itself. However, this flow doesn't support scenario outline cases.
Playwright and simple Cypress cases - To import cases, Junit file can be generated while running the cases - both frameworks do support generation. Once generated it can be imported in AIO via Import Results API or via Cycle -> Options -> Import Results, setting the CreateCase as true. This would create placeholder cases in AIO, with the title of the case being set and certain Automation fields being marked. Post creation, for Cypress and Playwright we have reporters, which can help you report results via easy to set config in their respective config files.

The cases created in AIO using the above flows, have an automation key set in them, which avoids duplication while usign the same caes again. However, it is recommended to map the AIO case keys in the automated cases .

Hope that clarifies your query.

Regards, Niharika