In some companies specially in J2EE domain builds are delivered from development team to the testing team to start the system testing. For example a new product XXX is being released to the testing team so the dev team will deliver a build to the Testing team. Now Testing team will do the testing and then will release the product to the client. Now there is a new version of the product coming up with the name XXX.1 and is being released to the testing team so this will be the second build and the time between these 2 builds will be called as build interval.
It is agreed upon interval b/n Dev Team and QA Team. For a product based company bosses (parent company managers) tell us the interval b/n each build so that even they can verify the build if some technical/human/hardware resource is lacking at offshore. During initial project meetings it has to be decided
In some companies specially in J2EE domain builds are delivered from development team to the testing team to start the system testing.
For example a new product XXX is being released to the testing team so the dev team will deliver a build to the Testing team. Now Testing team will do the testing and then will release the product to the client. Now there is a new version of the product coming up with the name XXX.1 and is being released to the testing team so this will be the second build and the time between these 2 builds will be called as build interval.
Its a period of getting two different AUT s from the developers.it means the gap b/w two different testing builds received from the developers to testing team
