#NMS REMEMBRANCE HOW TO#
#NMS REMEMBRANCE MANUAL#
#NMS REMEMBRANCE SKIN#
#NMS REMEMBRANCE SOFTWARE#
#NMS REMEMBRANCE CODE#

Validate executable speciications frequently to keep them reliable.

#NMS REMEMBRANCE HOW TO#

In the next chapter, I present some good ideas on how to get the most out of your set of executable speciications by evolving a documentation system. The speciications then become a living documentation system that explains the functionality. Once we have speciications that are continuously validated, it becomes easy to assert what a system does from a functional perspective, at least for the parts of it that are covered with executable speciications.

Long-term value comes from living documentation.

Looking at the end goal as business process documentation is a useful model.

There are many different ways to collaborate.

Living documentation as competitive advantage.

When: End-to-end use case traceability required.

Living documentation should be organized for easy access.

Living documentation should be consistent.

Avoid using technical automation concepts in tests.

Living documentation should be easy to understand.

When: Failing tests are disabled, not moved to a separate pack.

Automatically check which tests are turned off.

Create a known regression failures pack.

When: You can get more than one test Environment.

When: A small number of tests take most of the time to execute.

Avoid using in-memory databases for testing.

Break long test packs into smaller modules.

When: Working with temporal constraints.

When: External systems participate in work.

When: Working with external reference data sources.

Create simpler test doubles for external systems.

Set up a dedicated continuous validation environment.

Identify unstable tests using CI test history.

When: Working on a system with bad automated test support.

When: Specifying logic thatвЂ™s not data driven.

When: User interface contains complex logic.

Specify user interface functionality at a higher level of abstraction.

#NMS REMEMBRANCE SKIN#

Automate below the skin of the application.

DonвЂ™t check business logic through the user interface.

DonвЂ™t replicate business logic in the test automation layer.

Describe validation processes in the automation layer.

#NMS REMEMBRANCE CODE#

DonвЂ™t treat automation code as second-grade code.

#NMS REMEMBRANCE MANUAL#

Avoid automating existing manual test scripts.

When: Working with objects with many attributes.

When: Dealing with complex dependencies/referential integrity.

In order to: Make the test easier to understand.

When: Describing rules with many parameter combinations.

Start with basic examples then expand through exploring.

Use a descriptive title and explain the goal using a short paragraph.

DonвЂ™t get trapped in user interface details.

Examples should be precise and testable.

When: Requirements are impossible to quantify.

Illustrating nonfunctional requirements.

Avoid the temptation to explore every combinatorial possibility.

When: Working with enterprise customers.

Get basic examples directly from customers.

Ask for an alternative way to check the functionality.

Avoid using abstract classes of equivalence.

DonвЂ™t have yes/no answers in your examples.

Illustrating using examples: an example.

DonвЂ™t hinder discussion by overpreparing.

Undertake detailed preparation and review up front.

When: Business stakeholders are readily available.

Have developers frequently review tests before an iteration.

Why do we need to collaborate on specifications?.

Make sure teams deliver complete features.

Collaborating on scope without high-level control.

When: Business users trust the development team.

Have developers provide the вЂњI wantвЂќ part of user stories.

Understand what outputs the business users expect.

Understand where the value is coming from.

Watch out for organizational misalignment.

Watch out for tests that change frequently.

When: All details are required for sign-off.

When: Regulatory sign-off requires details.

Get sign-off on вЂњslimmed down use casesвЂќ.

When: Signing off iteration by iteration.

Get sign-off on exported living documentation.

#NMS REMEMBRANCE SOFTWARE#

Global talent management team at ultimate software.

When: Developers are reluctant to participate.

Track who is running-and not running-automated checks.

When: Introducing functional automation to legacy systems.

Keep one person on legacy scripts during migration.

DonвЂ™t make test automation the end goal.

When: Working in an environment thatвЂ™s resistant to change.

When: Developers have a good understanding of TDD.

Use test-driven development as a stepping stone.

User stories for a basic loyalty system.

Nms remembrance