Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

After running our normal automated tests against a test area, we releasing the change to production then run some additional tests against production to verify the roll-out ran correctly and to test some conditions that we can reasonably duplicate in testing. This testing is intended to catch errors after they are released, but before too many users see them.

Is there a standard term for this testing? I'm tempted to call it a smoke test, but that term is already used for testing packages.

Looks like this a duplicate of:

What would be a good term for continuous testing post-deployment?

share|improve this question

marked as duplicate by Kate Paulk, user246, corsiKa Nov 19 '13 at 20:23

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

I've always called it "smoke testing". In other questions I've given the same answer. It's not so important that you use an industry standard (Because often there isn't one), but more important that you use standard terms and definitions within your project and everyone understands their meaning. – Sam Woods Oct 24 '13 at 18:47
If we could agree on that within our project I wouldn't have asked it here. :) – Ben Martin Oct 24 '13 at 20:09
See also… – user246 Oct 24 '13 at 20:22
Can you clarify what kinds of tests you are running in production? For example, if you are running read only test that verify correct deployment of executables, that is one thing. If you are actually putting test data into the product database, that's entirely something else. – Chuck Krutsinger Oct 25 '13 at 19:04
Just using a tool like a user would. In my case these are internal tooling to create a sandbox, build some files, etc. – Ben Martin Nov 15 '13 at 19:50

I don't know if there's a standard.

We call this "Release Testing".

share|improve this answer

I have always called this Acceptance Testing, it doesn't matter who the Customer is running it (at least in my world, yours will differ) so long as it has a set of Agreed upon tests to run that can be said to "Accept the release to production".

Standards in Software depends on what general set of standards you follow, but mostly it's a "depends" answer, where it depends on your corporate culture and specific industry.

share|improve this answer

Considering ISTQB glossary I would name it 'Maintenance Testing'.

share|improve this answer

What about factory test: test to be run before going to factory, simulating the factory flow. In my team there is a difference between factory testing and release testing. Not all software releases end up in factory.

share|improve this answer
it wouldn't be preproduction, since it is done in production, acting like a user – Ben Martin Oct 24 '13 at 20:10
Some details in why you call them 'factory tests' would add some context to you response. – Suchit Parikh Oct 30 '13 at 20:36

Not the answer you're looking for? Browse other questions tagged or ask your own question.