Unit Testing

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Testing.xls

Box-Out.png
Exit

  • Testing.xls

Star.png
Solution

process-descending-24px.png
Process

Unit Testing1.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

  • Pruebas.xls

stuff.png
Examples

  • None

tool.png
Support Tools

start-flag.png
Initial Context

This product can be used in any project in which it should be tested separately tasks to be implemented according to a set of test cases previously identified.

This indicates the programmer what to do when he codes. The requirements appear as unit evidence. You know when it is over because all unit test are exceeded .The benefit that have about it the design, is that in the unit test is set what is important to the customer.

end-flag.png
Result Context

Developers get a series of unit results for each test case associated with a task.

cloud.png
Problem

Developers should be able to get unit testing test cases, separately, satisfactory to continue the process.

A small problem is that the test itself may have errors and this leads to unit tests do not perform their activities properly.

forces.png
Restricciones (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

  • If the unit tests do not work must be corrected as soon as possible. This is the most important part of team work. Because of this, balance must be kept in the time devoted to the performance of the tests and the correction of non satisfactory.
  • The pair of developer carried on each unit test cases separate tests.
  • The Pruebas.xls file is a generic document for all test types with unit testing box checked, which brings together all the test cases for a task.

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