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

info provides previous user executor information if same user executor is run twice #622

Closed
sixstone-qq opened this issue Feb 8, 2023 · 2 comments

Comments

@sixstone-qq
Copy link
Contributor

sixstone-qq commented Feb 8, 2023

Provided this test:

name: foo
testcases:
- name: same_user_executor_twice
  steps:
  - type: a_user_executor
    in: "First call"
    info: Info "{{.result.out}}"
    assertions:
      - result.out ShouldEqual "First call"
  - type: a_user_executor
    in: "Second call"
    info: Info "{{.result.out}}"
    assertions:
      - result.out ShouldEqual "Second call"

With this user executor:

executor: a_user_executor
input:
  in: {}
steps:
  - type: script
    exec: echo "{{.input.in}}"
output:
  out: {{.input.in}}

The output from venom v1.1.0 is:

❯ venom run foo.yml
          [trac] writing results/venom.log
 • foo (foo.yml)
        • same_user_executor_twice
                • a_user_executor PASS
                • a_user_executor PASS
                  [info] Info "First call" (foo.yml:7)
                  [info] Info "First call" (foo.yml:12)
                  [trac] writing results/foo.same_user_executor_twice.step.0.0.dump.json
                  [trac] writing results/foo.same_user_executor_twice.step.1.0.dump.json
Writing file results/test_results_foo.xml
final status: PASS

Note the second Info from line 12 must output Second call and not First call.

Let me know if you need any help on this?

Thanks for this amazing project!

@sixstone-qq sixstone-qq changed the title info provides previous user executor information if same user executor is run info provides previous user executor information if same user executor is run twice Feb 8, 2023
@sixstone-qq
Copy link
Contributor Author

Attempt to fix in #617

@yesnault
Copy link
Member

closed with #617

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

No branches or pull requests

2 participants