The CreatorCon Call for Content is officially open! Get started here.

Best practice for keeping ATF tests after a clone

wpatrickhames
Tera Guru

What is the best practice for keeping ATF tests after you clone down from production to sub-production instances?  

I believe that I read somewhere that you do promote your tests up to production, although you don't enable them to run (because, production - duh).  That way they clone down.  Can I get verification this is the best practice way to do so?

Thanks,

1 ACCEPTED SOLUTION

Gerald Onyia
Kilo Guru

Yes. This is best practice. This is exactly how it's done at my company.

It can be promoted all the way to PRODUCTION, but not enabled in PRODUCTION. This way, you never lose your ATF Tests in the lower environments after clone downs. The clone downs will include your existing ATF Tests. It also allows you to perform automated regression after each clone down for quality check.

This is especially useful, for companies like mine, who have almost 600 ATF Tests.

View solution in original post

14 REPLIES 14

wpatrickhames
Tera Guru

Thanks so much, Gerald.  The way you described it - I was thinking that I read that somewhere.  I just cannot remember where.  

Oh man, this is good stuff.  Appreciate the info, Brad!

jus_doggin
Tera Contributor

Yes, we promote to PROD as well-works well.  We run our roughly 250 tests nightly in QA after code drops, and have data preservers on sys_atf_test_result, sys_atf_test_suite_result and any reports using those tables.

Hey jus_doggin, what's your process/policy for running your tests?  Do you guys have a formalized write-up describing it?  I'm looking to implement something like this myself.