feat: chain the Java pipeline from the documents to the rendered tree - #220
Merged
Merged
Conversation
…, and hold every rendered oracle through it
Shape
CoverageBaseline:
This pull request changed no covered line. |
…sses behind one query
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.
Closes #96.
Chains the Java pipeline end to end. One entry,
Pipeline.render, runs parse, check, lowering, resolution and the Acceleo templates in one pass. The parity suite then holds every rendered oracle through that entry.What it proves
ParityTest,the composed union renders to the committed trees byte for byte, compares the rendered trees through the CLI file interface like every other oracle kind:minimalanddatatobundles/cli/target/parity/rendered/;minimal/rendered/,data/rendered/and_estate/rendered/taken together, file for file.RenderedTreeTest).models/minimal.resolveddeploymentis read only as the expected output of the resolution.render.launchnow reads the Resolved Deployment the build leaves in the parity output, asresolution.launchalready reads its extents there.REQ-033 witnessed (as agreed)
ResolvedDeploymentTest#theResolvedModelNamesNoKubernetesOrTraefikFieldchecks the shared part of REQ-033: no feature of the resolved model is named for a Kubernetes or Traefik field. The list of forbidden names is the production check's.minimal's model validating was already tested. The witness list is now 13 witnessed and 1 pending (REQ-035, on Slice 4: model and render the knowledge platform #201).Checks
./mvnw -B -ntp clean verifyinemf/is green, with coverage and mutation at 100%.npm run verifyis green.