Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

What should a QA know about ServiceNow cloning? Common interview questions?

venky6181
Tera Contributor

3 weeks ago

Hi everyone,

I’m a ServiceNow QA preparing for interviews and want to clearly understand the clone workflow and QA role during upgrades or environment refreshes.

Could anyone share:

  • What clone-related questions are usually asked in interviews?

  • What key points or responsibilities a QA should know before and after cloning (e.g., validations, exclusions, preserving test data, etc.)?

  • Any practical tips from your experience handling clones during upgrades?

Thanks in advance for the insights!

0 Helpfuls
  • 367 Views
4 REPLIES 4

AnjalPDijo
Giga Guru

3 weeks ago

Hi @venky6181 ,
Please refer to the below link which covers everything about cloning, including pre-clone and post-clone activities, exclusions, and best practices:
ServiceNow Clone Made Easy: A Practical Step-by-Step

Hope this helps!

Best Regards,
Anjal

0 Helpfuls

PrashantLearnIT
Giga Sage

3 weeks ago

Hi @venky6181 

 

All the questions related to the cloning activities that can be asked on interview can be checked from here: Article : ServiceNow Clone Made Easy – A Practical... - ServiceNow Community

 

Above contains detailed information about cloning activities which will QA to understand about it. 

********************************************************************************************************
Please appreciate the efforts of community contributors by marking the appropriate response as the correct answer and helpful. This may help other community users to follow the correct solution in the future.

********************************************************************************************************
Cheers,
Prashant Kumar
ServiceNow Technical Architect


Community Profile LinkedIn YouTube Medium TopMate
********************************************************************************************************
0 Helpfuls

Sarthak Kashyap
Mega Sage

3 weeks ago

Hi @venky6181 ,

 

Please check below points you should take care before cloning:

 

1. Make sure automated test cases, ATF data, and test records are backed up

2. Communicate with developers and stakeholders to list what needs to be retained

3. Verify the clone log for completion and errors

4. Check key functionalities — login, roles, ACLs, UI Policies, business rules, and integrations

5. Validate ATF test suites and make sure test data is intact

6. Check Notification, work flow, flow designer, all UI part is working or not, bcoz I saw many time in UI Builder some part got broke. So testing should done properly 

7. Keep a snapshot of key properties and sys_ids you don’t want overwritten

8. Work closely with the platform admin team — clones are technical, but QA validation is critical to avoid surprises.

9. Stop scheduled jobs or integrations that could trigger during the clone window and once Clone completed, Re-enable notifications, scheduled jobs, and integrations if needed

 

 

 

Please mark my answer correct and helpful if this works for you

Thanks and Regards,
Sarthak

 

0 Helpfuls

Shaqeel
Mega Sage
Mega Sage

3 weeks ago

Hi @venky6181 

 

How did your interview go?

I think now you can share the questioned asked here. 😄

 

Regards

Shaqeel


***********************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting "Accept as Solution" and " Helpful." This action benefits both the community and me.

***********************************************************************************************************************





Regards

Shaqeel
0 Helpfuls