Integration Testing

Question 1

What is integrations testing and what does it aim to do?

Answer 1

Test that the units when put together, satisfies the requirements or use cases (does what it should).

The purpose is to expose the defects in the interactions between components or other systems.

Question 2

What is meant by Continuous Integration Process?

Answer 2

It’s a Software development practice where the team integrates the work frequently. Each integration will be verified by an automated build (including test) to detect integration errors asap.

Question 3

What is a code repository?

Answer 3

It is a container for all the code that the project has.

Question 4

What is an automated build?

Answer 4

There are tools like Maven that will create automated builds, they are used to execute the code so that you can perform automated tests on them.

• You can build some parts of the components as standalone.
• You can upl

Question 5

What is a Continuous Integration Server and what does it do?

Answer 5

The continuous integration server acts as a monitor to the repository. Every time a commit against the repository finishes the server automatically checks out the sources onto the integration machine, initiates a build and notifies the committer of the result of the build.

Question 6

What is a integration environment and what should it look like?

Answer 6

It is the environment that the Continuous Integration tests happens in. It should mimic the production environment, which means that it should run on the exactly same versions and programs that it would once released.

Question 7

What are the advantages of The Continuous Integration Process?

Answer 7

It reduces risks and it is easier to determine how much time is needed to finish integration, by integrating small bits every day.
Maybe most important you will know be better at narrowing down where the error is, as you know with what code it came

Question 8

What is the overall process / general steps of CI?

Answer 8

• Upload to the mainline (repository / server)
• build and test on the server
• upload to the mainline if no mistakes are found or solve problems and retry to upload-

Question 9

What is the goals of a code repository?

Answer 9

• To be able to quickly export the program to a virgin machine and build correctly.
• Include everything in the code repository.
• Have a mainline and keep branches to the minimum.
• Keep everything needed for the build in the repository and keep the build products away from the repository.

Question 10

After the developer is done with a task what should he do if the team is doing CI?

Answer 10

• When he is done (usually multiple times a day) he should upload it to the CI server which will create an automated build and run the tests.
• If the tests pass and the the changes will be committed to the main branch and pushed.