Integration tests vnext - #17
Conversation
…data enrichment (derived from on-entry task results) into the state body. An extra test was also added for another state referenced under the exit transition’s onAvailable field
…d task logical group removed.
…cript task and 5th task type is considered as human task type
…nd scripts were the ones putting values there. That produced a lot of false positives—we were mainly checking that scripts ran, not that the tasks themselves behaved correctly. Now many tasks are actually tested.
…er) had been missing. For “condition”, supplying a rule was enough — there are already transitions that use rules. Nothing timer-related existed, so a transition that uses a timer was added.
… test. script base test logic added to docs.
…ectly and schema data test renamed as schema-validation test. schema-validation tests are completed.
…rors on tests, probably caused by wrong workflow definition.
|
Important Review skippedToo many files! This PR contains 260 files, which is 110 over the limit of 150. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (260)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Code Review
This pull request significantly updates the vNext Runtime platform reference and its integration tests. It introduces a comprehensive domain knowledge skill file, refines Postman and HTTP test collections to match C# integration tests, and reorganizes various workflow components including schemas, tasks, and views. A major part of the change involves standardizing labels and descriptions to English and enhancing test coverage for core features like error boundaries, schema validation, and version consistency. I have no feedback to provide as the existing review comment was filtered out based on the instructions.
No description provided.