cosmos / interchain-security

Interchain Security is an open sourced IBC application which allows cosmos blockchains to lease their proof-of-stake security to one another.
https://cosmos.github.io/interchain-security/
Other
154 stars 115 forks source link

fix: print test name instead of config name #1961

Closed p-offtermatt closed 3 months ago

p-offtermatt commented 3 months ago

Description

Fixes a bug where the e2e framework would output the name of the config, not of the step choice (which is much more descriptive).

Now both are displayed.

Output before:

------------------------------------------
Test name : default
Target: 
Docker
        Consumer version: default (current workspace)
        Provider version: default (current workspace)
        Docker image: cosmos-ics:local
        Docker container: interchain-security-instance
------------------------------------------

output after:

------------------------------------------
Test name : happy-path
Config: default
Target: 
Docker
        Consumer version: default (current workspace)
        Provider version: default (current workspace)
        Docker image: cosmos-ics:local
        Docker container: interchain-security-instance
------------------------------------------

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

I have...

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

I have...

Summary by CodeRabbit

coderabbitai[bot] commented 3 months ago
Walkthrough ## Walkthrough Recent changes in the end-to-end test files involve updating the `steps` field to `stepChoice` within the `testStepsWithConfig` and `TestRunner` structs. This adjustment ensures that `steps` are now directly associated with `StepChoice`, enhancing configuration management and test execution. Additionally, function signatures and method references were updated to align with this new structure, improving clarity and maintainability. ## Changes | File Path | Change Summary | |----------------------------|-------------------------------------------------------------------------------| | tests/e2e/main.go | Updated `testStepsWithConfig` struct's `steps` field from `Step` slice to `StepChoice`. Modified `getTestCases` function to use `stepChoices[tc]` directly. | | tests/e2e/test_runner.go | Changed `steps` field to `stepChoice` in `TestRunner` struct. Updated `CreateTestRunner` function signature and method references to match the new structure. | ## Sequence Diagram(s) ```mermaid sequenceDiagram participant User participant TestRunner participant TestStepsWithConfig participant StepChoice User->>TestRunner: Run() TestRunner->>TestStepsWithConfig: Initialize with StepChoice TestRunner->>StepChoice: Execute steps StepChoice-->>TestRunner: Return results TestRunner-->>User: Display results ``` This diagram illustrates the updated control flow where `TestRunner` now interacts with `StepChoice` directly, encapsulating the steps within the `StepChoice` structure.

Recent review details **Configuration used: .coderabbit.yml** **Review profile: CHILL**
Commits Files that changed from the base of the PR and between 5d6f31381be879e1fa18c216aa8361c6524974e5 and f34528ddc8e7d0cd396c54ae8780956d467d1d41.
Files selected for processing (2) * tests/e2e/main.go (3 hunks) * tests/e2e/test_runner.go (5 hunks)
Additional context used
Path-based instructions (2)
tests/e2e/test_runner.go (2) Pattern `**/*.go`: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations. --- Pattern `tests/e2e/*`: "Assess the e2e test code assessing sufficient code coverage for the changes associated in the pull request"
tests/e2e/main.go (2) Pattern `**/*.go`: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations. --- Pattern `tests/e2e/*`: "Assess the e2e test code assessing sufficient code coverage for the changes associated in the pull request"
Additional comments not posted (5)
tests/e2e/test_runner.go (4)
`121-127`: The updated `CreateTestRunner` function correctly initializes `TestRunner` with `stepChoice`. Good use of structured initialization. --- `136-139`: Including `tr.stepChoice.name` in the output enhances clarity and aligns with the PR objectives. --- `149-156`: The updated `Report` method now correctly includes `tr.stepChoice.name`, enhancing the detail and usefulness of the reports. --- `22-22`: Change from `steps` to `stepChoice` aligns with the PR objectives for more descriptive step handling.
Verification successful --- The `StepChoice` struct includes a `steps` field, confirming that the usage of `tr.stepChoice.steps` in `test_runner.go` is correct and consistent with the new structure. - `tests/e2e/main.go: type StepChoice struct { name string, steps []Step, description string, testConfig TestConfigType }`
Scripts executed The following scripts were executed for the analysis: --- Script: ```shell #!/bin/bash # Description: Verify all references to `steps` are updated to `stepChoice`. # Test: Search for the old field usage. Expect: No occurrences. rg --type go $'steps' tests/e2e/test_runner.go ``` Length of output: 114 --- --- Script: ```shell #!/bin/bash # Description: Verify the definition and usage of `stepChoice` to ensure it includes a `steps` field or equivalent. # Test: Search for the definition of `stepChoice` to understand its structure. rg --type go 'stepChoice' tests/e2e/test_runner.go # Test: Search for the definition of `StepChoice` to understand its structure. rg --type go 'StepChoice' tests/e2e/ ``` Length of output: 731 --- --- Script: ```shell #!/bin/bash # Description: Verify the structure of `StepChoice` to confirm it includes the `steps` field. # Test: Retrieve the definition of `StepChoice` to confirm it includes the `steps` field. rg --type go 'type StepChoice struct' -A 10 tests/e2e/main.go ``` Length of output: 178
tests/e2e/main.go (1)
`280-280`: The change of `steps` to `StepChoice` in `testStepsWithConfig` is consistent with changes in `test_runner.go` and enhances clarity.
--- Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.