Talk:System integration testing

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
???	This article has not yet received a rating on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.

Isn't this the same as Integration Testing or are there moron bureacrats who view this as an extra step after I&T?

Can we replace the word "shakesdown" - I don't understand what it means. I'm not a software developer, but I've just come across a document on our intranet which shows Development --> SIT --> Regression so i wanted to understand what "SIT" and "Regression" means - and I can't fully understand what "shakesdown" means when refering to programming.

There is a distinct difference between Integration Testing (sometimes called Integration Testing in the small) and System Integration Testing (Integration Testing in the large). integration testing confirms that the units of a single system co-exist. Whereas System Integration testing confirms that multiple systems co-exist.

Once a system has been tested using a suite of tests there may be future releases. Regression Testing is the re-running of those previous tests to ensure that the system has not been regressed by any of changes.

I agree that System testing tests the integration of components into a system, and that System Integration testing tests the integration of systems. So, we probably shouldn't merge. Also, there's a statement about SIT being similar to unit testing. I strongly disagree with that. They're at two opposite ends of the spectrum. DRogers 16:16, 3 October 2006 (UTC)[reply]

More on SIT

System Testing and System Integration Testing should be discussed in different modules.

Kallol (13th Nov, 06)

I guess we are clear about the difference between System Testing and Integration Testing. Even though they can be categorised as two different types of testing, they can be interchangably used (to some extent). For example, testing a few modules combined for flow in your software package can be called Intregration Testing, but testing all the modules combined for all possible flows can be called Integration Testing as well as System Testing.

System Integration Testing, can be defined as taking the best approach of both System and Integration Testing and doing it as a single test (depending on your needs and the demands of your software).

Like the previous comment by DRogers, claming that SIT is similar to Unit Testing, is preposterous !

Vijay (10-OCT-2006)

Well, the way I see it,has integrating modules can be called Module Integration (though usually shortened to Integration). Integrating subsystems can be called Subsystem Integration. Integration systems can be called System Integration. I think I see a pattern. The real question is, what is the scope of each article, and what is the overlap? DRogers 18:05, 10 October 2006 (UTC)[reply]