Writing Functional Tests

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

  • Customer Ideas

Box-Out.png
Exit

  • Testing

Star.png
Solution

process-descending-24px.png
Process

Writing Functional Tests1.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

  • Ideas_Cliente.doc
  • Pruebas.xls

stuff.png
Examples

  • Proyecto C3 de Daimler-Chrysler.

tool.png
Support Tools

start-flag.png
Initial Context

This product can be used in any project to be carried out tests on scenarios described by the customer.

end-flag.png
Result Context

The team, including customers, get a set of scenarios that test the written code.

cloud.png
Problem

The test project manager must be able to translate the client's ideas into actual testing of the technical field. He must also use these ideas of the client as a starting point for variations that will probably fail the generated software.

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 it need urgent application or dispose of some of their funcionalidades.

roles.png
Roles

  • Test Manager (1)
  • Area of business users (2 at most)

lightbulb.png
Lessons Learned

  • Customers write test story to story. You should ask what would have to prove before being sure that the story at issue is completed. Customers need a tool that allows them to write, execute, inspect and maintain functional testing, ie, a kind of translator between the language of the client and the technical part.
  • The test project manager meets with customers and transforms their real ideas and expectations about the software scenarios (test cases) that can be performed within the technological field.
  • The input document Client Ideas and customer expectations of the functionality expected to perform the software.
  • The output document test is a generic file type .xls (Microsoft Excel), for all test types with the box user test marked, which includes the translation of the client's ideas, in the language of the technical field, to test scenarios of the generated software.

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