Modify Test Cases

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

Modify Test Cases1.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

  • None

bricks.png
Related Patterns

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 that once executed the cases, any of these cases is not satisfactory because it has not provided any concrete evidence casuistry.

end-flag.png
Result Contextt

Developers get modified test cases, adding or removing elements, either by lack of breadth in scope or excess.

cloud.png
Problem

Developers should be able to determine whether the identified test case is complete and decisive, otherwise it can be modified appropriately. Modification of test cases can be performed under these circumstances, including:

  1. If there is a problem, write a test that isolates it.
  2. If you are doing recoding in some code, and you are not sure how they should behave, and there is still no evidence for such behavior in question, write a first test.

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 for use::If you need urgent application or dispose of some of its functionality.

roles.png
Roles

  • Developers (2-12)

lightbulb.png
Lessons Learned

  • The pair of programmers should revisit the task related to the case of unsatisfactory test. The activity of correcting the test cases is the most important of which must make the members of the team, although the balance between time devoted to the implementation of testing and correcting them must be maintained.
  • If the test case is unsatisfactory it should be retested task to modify test cases identified.
  • The tests file is a generic document for all test types with unit testing box checked, which bind all test together cases for a task. We must pay special attention to those cases of unsatisfactory test, it must be modified. You can add or remove test cases as deemed appropriate.

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