Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: add a missing assertion chain for the response entity - INS-3917 #7474

Merged
merged 2 commits into from
Jun 3, 2024

Conversation

ihexxa
Copy link
Contributor

@ihexxa ihexxa commented Jun 3, 2024

Changes

  • Supported negative assertion chain such as insomnia.response.to.not.have.status(200);
  • Added utests
  • Only keep one instance for collectionVariables and baseEnvironment so that operations triggered from different entities will take effect.

Ref: - INS-3917

@ihexxa ihexxa self-assigned this Jun 3, 2024
@@ -140,7 +139,7 @@ export async function initInsomniaObject(
const variables = new Variables({
globals,
environment,
collection: collectionVariables,
collection: baseEnvironment,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is collection accepting environments? If so maybe we should change the name to make more clear

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, it tries to keep one one base environment instance so that operations triggered from variables would also be applied to the base environment.
Let me start another PR to rename them.

@ihexxa ihexxa enabled auto-merge (squash) June 3, 2024 08:54
@ihexxa ihexxa merged commit 42cd078 into develop Jun 3, 2024
7 checks passed
@ihexxa ihexxa deleted the fix-response-assert branch June 3, 2024 09:08
@ihexxa ihexxa changed the title fix: add a missing assertion chain for the response entity fix: add a missing assertion chain for the response entity - INS-3917 Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants