File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Testing and the fly likes Some industrial terms need to be understood Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Testing
Bookmark "Some industrial terms need to be understood" Watch "Some industrial terms need to be understood" New topic

Some industrial terms need to be understood

jazy smith
Ranch Hand

Joined: Nov 18, 2009
Posts: 101
Hi all,

I am a fresher in IT industry. I have heard few software development words like " development, Integrated System Test environment, System Test environment, User Acceptance environment, Production Environment " Performance Test

I need to understand the correct sequence of above environments. Example, when does the IST environment comes into picture. when does UAT comes into picture.

Typically what I understood is the below sequence. Please correct me if I am wrong

Dev -> Integrated System Test -> System Test (Staging) -> User Acceptance Testing (UAT environment) -> Production
Jeanne Boyarsky
author & internet detective

Joined: May 26, 2003
Posts: 33130

We don't use the term "Integrated System Test" (we do use Integration Test so I assume it is the same thing.) I agree with your order.

[OCA 8 book] [Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Jeffrey Hunter
Ranch Hand

Joined: Apr 16, 2004
Posts: 305
Good luck, jazy. I agree with your order as well. Unfortunately some of the industrial terms you'll come across will have dubious meanings. The best thing you can do is work for a place that clearly defines what all these "industrial terms" mean -- because believe me, they will mean different things to different people. I recently received an email from a customer that had a virtual flurry (no, better categorized as a blizzard) of all the testing buzzwords: unit testing, acceptance testing, system testing, functional testing, and blah blah. The customer wanted to make sure we were doing all these things.

At my place, we have Test Levels to define the scope of the test:
  • System Test
  • Integration Test
  • Focused Test
  • Unit Test

  • Then, we have Test Types to describe the objective of the test:
  • Functional Testing
  • Performance Testing
  • Usability Testing
  • Compliance Testing
  • Security Testing
  • Acceptance Testing

  • So, in a nutshell, we use Test Levels to define "how much" of the system we are going to test; and we use Test Types to define "what" we are going to test for. This might seem complicated, but when you have customers sending emails based on industrial buzzwords, it's important to establish a common vocabulary (all part of managing expectations).
    I agree. Here's the link:
    subject: Some industrial terms need to be understood
    jQuery in Action, 3rd edition