Repository navigation
test(e2e): write the GEMMA plate peers and previous-catalogue import specs - #2117
Closed
rubenvdlinde wants to merge 1 commit into
Closed
rubenvdlinde wants to merge 1 commit into
rubenvdlinde wants to merge 1 commit into
Conversation
Nineteen spec files the tasks of open changes point at were missing. They are written from each change's @e2e scenarios over the real page ids, routes, labels and test ids, not yet run against a live instance; scenarios whose UI is not built are test.fixme with the reason. Assisted-by: ClaudeCode:claude-opus-5-5
Contributor
Author
|
Closing: opened on a leftover branch name whose old commit was already merged in #2102, so this PR shows that commit instead of the new specs. The new specs follow on cloud/b-stackiq-e2e-peers-legacy. Generated by Claude Code |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Writes the two Playwright spec files that open tasks name and that were missing. Both come from the changes' scenarios and have not been run.
tests/e2e/spec-coverage/gemma-plate-peers.spec.ts(gemma-plate-views-peers-and-definitions, task 4, REQ-GPL-002). It seeds an own municipality, three comparable ones and one outside the inhabitants band. The endpoint case checksGET /api/reference-component-coverage/peers: it returns the type and band, the peer applications appear, and no organisation is named. The table and side-panel cases are marked fixme, because the layer is not on development yet (it is in feat(stackiq): build gemma-plate-views-peers-and-definitions #1974).tests/e2e/spec-coverage/legacy-catalogue-import.spec.ts(landscape-migrate-from-previous-catalogue, task 4, REQ-LCM-001 to 003). Every case is marked fixme until the profile, the endpoints, the dialog and the fixture exist. tasks.md has a note saying so.No task is ticked: e2e tasks stay open until the specs run against a live instance.
Checks
lib/Lifecycle/ArchitectureDecisionReviewGuard.phpandlib/Service/Registration/ServiceFactories.php. This PR does not touch either file, and development fails the same way.npm run lint: the same 21 errors as development, none in these files.composer check:strictcould not run.composer installcannot finish in this container because GitHub answers 403 to the phpstan dist download (api.github.com/repos/phpstan/phpstan/zipball/...), and the lock has no source for that package. The PR changes no PHP, so the PHPUnit failure set is the same as development.Generated by Claude Code