Scream testing is a practice used to determine whether a legacy service, server, API, or component is still in use by temporarily disabling or shutting it down and waiting to see if anyone complains "screams".  In modern software architecture and cloud infrastructure, orphan dependencies and zombie assets frequently remain active without clear documentation or ownership. While it carries operational risk and should be treated as a last resort with an immediate rollback strategy, scream testing helps teams identify hidden downstream dependencies, clean up technical debt, and decommission unused systems safely. 

migration testing is the process of verifying that data, applications, or systems work correctly after being moved from one environment, platform, database, or version to another. Think of it like moving houses you want to make sure nothing got lost or broken in transit.

Testing is about uncovering risks and any evidence gathered  during testing is filtered and transformed by tester who then shares a narrative on what is happening with product and what it actually mean... it may also include lot of processes such as modeling, questioning , studying , sampling , observing, sensemaking, and storytelling...which can be done by skilled human or toolsReference : Taking Testing Seriously by James Bach and Michael Bolton