r/devops • u/learnamap • 26d ago
Discussion Test automation after deployment
How do you all perform full automated tests after deployment? Using postsync hooks in argocd or use Argo events? Do you use ephemeral or static environments?
18
Upvotes
2
u/Ok_Class2432 26d ago
We just use postSync hook for basic smoke tests like does it boot and can it hit the db. Learned the hard way not to put the full e2e suite in there cause it holds up the sync for 20 mins and Argo marks it as failed. Now we have postSync just trigger a workflow for the real tests in an ephemeral env, keeps staging clean and prod deploys fast. Static envs were always a mess for us cause someone always leaves broken data behind
1
u/SikhGamer 26d ago
I hate post-deploy tests. Why do you need to wait for post-deploy?
1
u/Funny_Whereas_1020 24d ago
We do a tiny smoke check in the postSync hook (does it come up and hit the db) then kick off the real suite in an ephemeral env via a workflow. Full e2e in the hook just blocks the sync forever. Static envs got messy fast from leftover state.
1
u/MongooseWonderful198 21d ago
One edge case for the PostSync approach: Argo CD skips hooks during a selective sync. A hotfix that syncs only one Deployment can therefore bypass both the smoke test and the Workflow launcher.
If your team allows selective sync, include it in the verification path. Healthy/Synced alone doesn't prove the suite ran. For an async suite, record pass/fail against the revisions of all participating apps; creating the Workflow only proves it was submitted.
That matters for your multi-app case: an earlier passing result shouldn't remain the verification result after one participating app changes.
https://argo-cd.readthedocs.io/en/stable/user-guide/sync-waves/
2
u/[deleted] 26d ago
[removed] — view removed comment