Integration Test

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Testing

Box-Out.png
Exit

  • Testing

Star.png
Solution

process-descending-24px.png
Process

Integration Test.png

time-24px.png
Development time

    • To acquire the necessary knowledge to develop the software product:
    • To create the Product Pattern: 45 minutes.
    • To apply the Product Pattern:


video-24px.png
Explanatory video

  • Not applicable

Search-32px.png
Quality Controllers

  • None

template.png
Templates

  • Integración_Continua.doc

stuff.png
Examples

  • None

tool.png
Support Tools

start-flag.png
Initial Context

This product can be used in any project that, once made the job of integrating the individual work of a member of the team, it should be tested in conjunction with the work done by the other team members.

Integration testing is always carried out before adding any new class to the project, or after modifying any existing.

end-flag.png
Result Context

Developers get a result that shows them the ability to integrate their code with other work of their peers. Code duplication and redundancy is verified with the work of other partner.

cloud.png
Problem

Testing should be done in minutes. Too long integration tests diminish time to the developer to proceed with the development of their work and thus to the identification, formulation and addition of new test cases to integration.

forces.png
Restrictions (Forces)

  • Characteristics of organizations: This pattern can be used in existing projects in any company.
  • System Type to develop This product can be used in projects in which user requirements are changing.
  • Type of Customer: It must exist or be achieved, the target area development business being involved in achieving it.
  • Heuristics of use::If you need urgent application or dispose of some of their funcionalidades.

roles.png
Roles

  • Developers (2-12)

lightbulb.png
Lessons Learned

  • These tests should be performed every few hours (1 day maximum). Whenever you are working on a task, there are hundreds of things in mind. Work continues until there is a natural break (no more elements in the list of tasks) and then integration and its associated tests are done. The cycle must learn / test / program / version.
  • The tests file is a generic document for all test types with unit testing box checked, which bind all test cases for a task. We must pay special attention to those cases of unsatisfactory test, it must be modified. In this document their responsible and history associated is reflected. Corresponding to the test results and associated comments field is filled.
  • Gotta try together individual work with the work done by the other team members.

award.png
Capability Level

  • Not applicable.

Options.png
Basic Knowledge and Skills

board-24px.png
Knowledge

  • Knowledge of coding standard that defines the shared code ownership and the rules for writing and documenting code and communication between different pieces of code developed by different teams. Programmers have to follow the so that the code in the system look like if it had been written by one person.
  • Knowledge of the common vision of how the program works in which the activities take place.


help-24px.png
Abilities

  • Ability to work in group. All on an XP computer contribute in any way they can.
  • Predicting what will be completed by the deadline, and determining what to do next.
  • Programming capability in pairs. Besides to generate better code and tests, used to communicate knowledge through teams.

Information-Sources.png
Information Resources