ATF : should you move to them to production for cloning purposes ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2024 01:58 PM
Greetings All !
We wanted to know if we should move our ATF to production instance for cloning purposes ?
right now whenever we clone prod to non prod instances the some ATF config gets impacted and then we need to roll back.
Should we move our ATFs to production and disable them and then clone ?
- Labels:
-
Architect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2024 02:02 PM
We are syncing the test cases to our enterprise git by creating branches during every backup.
This is the best possible way that worked for us
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2024 03:47 PM
We are not mature enough. Do you think moving ATF to prod is a general practice or ATF remain in non prods.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2024 03:55 PM
we did not move the ATF to prod. as we dont have stable ATF tests and we keep updating them regularly.
moving the ATF to prod is good. if you dont have alternative way for backup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2024 04:31 PM
Yes. I suggest moving the ATFs to production. This helps in
- cloning ATFs back to lower environments during an upgrade
- creating reports that reference ATFs in production such as ATF coverage. Since the test cases are maintained in production it needs to reference ATFs to provide the right insights
