logofx/samples.specifications

This sample demonstrates how to use specifications and convert them to the acceptance tests.

Samples.Specifications

One of the missing points in the software development cycle often lies in the gap that develops over time between the initial product specifications, as stated by the product managers and their actual implementation/interpretation as carried out by the developers. This can be addressed by creating a unit/integration test suite which will provide a safe net for future changes. However having only unit/integration tests will preserve the gap as the product managers are not familiar with the code and the actual testing/isolation frameworks that the developers chose to use, if any. Therefore there's a need in bridging between the product managers/business experts and the development team. This issue can be addressed by using a dedicated behavior-specifying framework. For documentation go to https://github.com/LogoFX/Samples.Specifications/wiki

samples.specifications's Issues

Inconsistent selection behavior in end-to-end tests

TestStack.White.UIItems.ListViewRow cannot be selected normally. The method Select() doesn't work. For selection emultaion we use trick:

listViewRow.Focus();
listViewRow.Cells[0].Click();

But this trick works unstable. It is better add big delay between Focus() and Click():

listViewRow.Focus();
Task.Delay(1000).Wait();
listViewRow.Cells[0].Click();

Total cost is not refreshed when the cost change is discarded

Repro steps:

1. Open the app
2. Login
3. Select an item
4. Edit price (total cost changes)
5. Discard the changes

Expected: total cost is restored to its initial value
Actual: total cost doesn't change

The press of the enter key in Login Dialog must move focus to next control or to execute the Login Command.

Then focus is in User textbox, the press of the Enter key must move focus to password control. Then focus is in password, the press of the Enter key should cause to execution of Login command.

BRANCH WIZARD: The first editable input field in create/edit scenario must be focused on view activation

Use dedicated build jobs for every configuration

Should define specific .yaml files for each one of the 4 available configs:

• EndToEndWithFake - should build the client in DebugWithSpecs config and the e2e specs in EndToEndWithFake config

• IntegrationWithFake - should build the integration specs in IntegrationWithFake config

• EndToEndWithReal - should build the client in DebugWithSpecs config and the server in DebugWithSpecs config and the e2e specs in EndToEndWithReal config

• IntegrationWithReal - should build the integration specs in IntegrationWithReal config and the server in DebugWithSpecs config

BRANCH WIZARD: On press of Enter key the next focusable control should be focused

Pay attention, if focus is on last available focusable control in the flow, the press on Enter key should call to an Apply command.

The close guard is missing in edit/new state.

Then I edit new or existed record and click to window close button, the application is closed without a confirmation. In my opinion, it's a good use case sample to specification, since it one of the frequently tested problems in real applications.

The expected behavior is following:
Then [I click Windows close button ("x") or application "Close" button] and I have unapplied changes in the form, I want to see a guard message.
There are three options with a guard message box expected:

1. Save == to save changes and close the app;
2. Don't Save == exit without to save;
3. Cancel == do not exit.

Interesting case: what should happen, if I press "Save" and have invalid data, or I press "Save", but the save operation is failed?

Put the projects into dedicated folders by layer

Add the following folders:

• client
• server
• specs
• devops

Put the existing code and scripts according to their area

BRANCH WIZARD: Create use case and test to erroneous user/password input

BRANCH WIZARD: Add validation use case and test for create/edit view inputs