Skip to main content

Release 0.1.145

Verify on legacy app now lets the agent choose which scenarios to drive, takes your instructions, and keeps the legacy app's screens per feature. A feature or module with open warnings has a Warnings tab and can Continue fixing. Implementing a module brings every feature's work onto its branch, and the module page shows what its branch and features need. Every enabled validation rule is now checked, with no Applies when condition.

Upgrade notes​

  • Database migrations run automatically during the upgrade. They record scenarios the agent left out of a legacy check, the instructions given to it, and which screens show which scenarios; they also change the defaults for new projects' test runs.
  • Validation rules lose their Applies when text. The field is removed and existing text is discarded. A rule that only concerns some changes should now say so in its own text.
  • repave validation-rules no longer takes --applies-when.
  • No changes to .env or docker-compose.yml.

New​

Verify on legacy app chooses what to verify. When you verify a feature or a module, the agent reads the whole feature and its code, then drives every high-value scenario, main path first: each rule, validation, data change, message and screen. It may leave out a scenario another one already shows, or one something blocks; that scenario reads Legacy: Not verified with the agent's reason, and Verify again checks it on its own. A scenario that already had a result keeps it.

Instructions for the agent. The Verify dialog now has an optional Instructions for the agent box, for example "check the price rules first; the test login cannot open Administration". Once some of a feature's scenarios have a result, its dialog also asks which to verify, as a module's does.

Screens belong to the feature. The Legacy Screens tab shows one grid of the feature's screens, the ones the agent kept first, each with its caption and the scenarios it shows. Checking a feature again replaces a screen with the same caption rather than adding copies. The status filter now counts screens.

Warnings tab and Continue fixing. A feature that reads Implemented with warnings has a Warnings tab listing what each check still found; click the amber status to open it. Continue fixing picks the implementation up at the first check that ran out of review rounds, gives that check and every later one fresh rounds, and does not repeat the earlier ones. A module's page has a Warnings tab too, with one Continue fixing for every feature on it. Both need the Editor role.

The module page shows what its branch needs. Above the tabs, a module's page shows a merge conflict on its branch with Open in Repave IDE, a base branch that has moved on with Merge <base>, and, while it is in review, its pull request with Address N comments and SonarCloud's quality gate. On the Gherkin tab, a feature that needs someone is marked paused — needs you, failed or last job failed, and picking it shows the same banners and actions as its own page.

Improvements​

Implement module brings every feature's work. Features you leave unticked, and locked ones waiting for UAT or completed, now have their work brought onto the module's branch too, without being implemented again. A merged feature, or one in review, is left where it is. The run waits while a feature is still being implemented on its own or has a job in progress, and says which.

Every enabled validation rule is checked. Nothing decides on your behalf that a rule does not apply to a feature or prototype and skips it. The Applies when field is gone from the rule editor and from extracted rules.

New projects land work without waiting for the full suite. All three Test runs options in Project Settings are now on for a new project; untick one to have that run happen. Existing projects keep their choices.

Update feature branches covers every feature branch, whatever state the feature is in: in progress, merged, or a prototype not yet implemented. The automatic update does the same.

Compare code shows every file in one scroll. Each side lists all its files one after another; the file buttons jump to a file, and the arrow beside a file's name folds it away.

Bigger screenshots in the legacy run dialog. The step's screenshot fills most of the dialog, and a click shows it full size, with Previous and Next through the steps.

Fixes​

  • A daily test run of a large suite could report "The suite ran, but found no scenarios" after running every one, because the test report grew too large to write. Traces are no longer copied into the report, an existing project's test hooks are updated the next time a feature or fix runs its tests, and a run whose report is empty now reads Could not run and names the runner's log.
  • Writing tests for a module could fail a feature whose tests passed, as "reported nothing for this feature".