Diferencia entre revisiones de «Functional Test Story»

De productpatterns_wiki
Saltar a: navegación, buscar
Línea 44: Línea 44:
*[[Writing Functional Tests  | Writing Functional Tests Pattern]]
*[[Writing Functional Tests  | Writing Functional Tests Pattern]]
*[[Writing Test Cases  | Writing Test Cases Pattern]]
*[[Writing Test Cases  | Writing Test Cases Pattern]]
*[[Modify Story in Tasks  | Modify Story in Tasks Pattern]]
*[[Change Story in Tasks  | Change Story in Tasks Pattern]]
*[[Writing Story  | Writing Story Pattern]]
*[[Writing Story  | Writing Story Pattern]]

Revisión de 16:19 29 mar 2015

Spanish.jpg Español


  • Testing


  • Testing



Functional Test Story1.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:

Explanatory video

  • Not applicable

Quality Controllers

  • None


  • Pruebas.xls


  • None

Support Tools

Initial Context

This product can be used in any projectin which functional test should be performed about the generated software.

From user stories functional tests are made and each may correspond one or more. It is not considered that a story is complete until you pass all your functional tests. The functional tests should be done before you start debugging.

Result Context

Responsible for testing and customers get a glimpse of the percentage of successful test in order to establish the degree of project progress.


The client should be provided with a tool powerful enough to translate their ideas into a set of scenarios on which to test the software. In addition, the tool must allow the execution and maintenance of the scenarios described by the ideas of the customer.

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.


  • Test Manager (1)
  • Business Area Users(2 at most)

Lessons Learned

  • Not all functional tests have to function at 100% at the same time. The results of functional tests can not be binary, as in the case of unit testing, since they come from different codes generated by different developers team. Over time, correcting the functional tests, the results of approach 100%. As you become closing one version, the client need to classify functional tests to be failing, establishing a priority for correction.
  • The client uses the software generated in each of the scenarios described.
  • Textual Input document is a generic .xls (Microsoft Excel), for all test types with user box marked tests, which includes the translation of the client's ideas, in the language of the technical field, to tests scenarios of the software generated. In this paper, in the output, percentage of customers satisfaction after performing the corresponding functional tests are added. Also included priority for correction of functional tests that were not satisfactory.

Capability Level

  • Not applicable.

Basic Knowledge and Skills


  • 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.


  • 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 Resources