Skip to content

Option to automatically set Automation Key to match Test Key?

C

cameron.fairburn

81 views

Hello, the way we integrate our automated tests with our AIO test cases means that using the Test Key of each test is the most effective way to link tests.

Right now, this is a manual process which has some risk, if we re-index we would have to redo all of the keys in AIO which would definitely not be feasible.

I am wondering if it makes sense to create a config option, which if checked will automatically set all Automation Keys to match the Test Key of every test case?

Replies

6
Join to participate

Start threads and reply to conversations.

C

cameron.fairburn

Hi N,

I am not sure if it is a very specific use case, because this is a guaranteed way to align automation keys and titles in any automation framework.

Is there any reason other than re-indexing that makes you think this is a bad idea? Otherwise what is the purpose of the test key, as keys ideally should be immutable.

Thanks,

Cameron

N

Niharika

Hello @cameron.fairburn ,

Apologies for missing this. If we automatically set the automation keys to the case keys, then on re-indexing, the automation key may be, say AT-TC-12 and the case key may have reindexed to AT-TC-10. Now there can be another case, which has been newly reindexed to the case key - AT-TC-12.

When a user marks the tag of the case as AT-TC-12, we would get to two cases , one with automation key as 12 and one with case key as 12. This would cause a problem and incorrect cases will be updated.

Even if the functionality was given, then after running the utility, the casekey and auto key would become AT-TC-10 and the automation case in the automation repo would still be pointing to AT-TC-12.

So, in both cases, this solution wouldn't work. However, we do understand reindexing creates a problem with automation and will discuss internally if a solution can be provided to address it.

Regards,

N

FD

floramae Dani Kilan

Hello

N

Niharika

Hello Cameron,

Automation keys created by AIO on import results are normally fully qualified names corresponding to code structure. Putting the test key as automation key seems to be a very specific use case.

One of the ways to achieve this is to use the APIs to update the automation key. You can reindex and then use the REST APIS of Get Case and Update Case to update the automation key to the latest case key.

Hope that helps.

-N

Browse all replies