refactor: e2e tests

[marcusschiesser]

Summary by CodeRabbit

• Bug Fixes

  • Improved test execution logic for the extractor template based on environmental variables to ensure more accurate test coverage.
  • Streamlined the test suite for the streaming template to enhance clarity and coverage by removing unnecessary conditionals.

• New Features

  • Enhanced configurability of tests based on specified frameworks and data sources, allowing for more precise control over test execution.

• Chores

  • Simplified the CI/CD workflow configuration by removing outdated templates and exclusion rules.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e6802b7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The changes primarily involve modifications to the GitHub Actions workflow and test files, including the removal of template configurations and the introduction of new conditional logic based on environment variables. The workflow has been simplified by eliminating certain templates and exclusions, while the test files have been restructured to enhance control flow and focus on specific templates without conditional checks.

Changes

Files	Change Summary
.github/workflows/e2e.yml	Removed templates, exclude sections, and TEMPLATE environment variable from job configuration.
e2e/extractor_template.spec.ts	Introduced templateFramework and dataSource constants; expanded conditional logic for test execution.
e2e/streaming_template.spec.ts	Removed templateType variable; hardcoded "streaming" and simplified test execution structure.

Poem

🐇 In the meadow where templates play,
Changes sprout like flowers in May.
With fewer checks and clearer streams,
Our tests now dance in joyful dreams.
A hop, a skip, to CI's tune,
Let’s celebrate beneath the moon! 🌙✨

---

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
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • 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 Configuration 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1ffd3c9 and e6802b7.

Files selected for processing (3)

• .github/workflows/e2e.yml (2 hunks)
• e2e/extractor_template.spec.ts (1 hunks)
• e2e/streaming_template.spec.ts (2 hunks)

Additional comments not posted (9)

.github/workflows/e2e.yml (3)

Line range hint 1-30: Verify the impact of removing the templates section.

The removal of the templates section simplifies the configuration but may reduce flexibility. Ensure that the workflow still meets all requirements without this section.

---

Line range hint 1-30: Verify the impact of removing the exclude section.

The removal of the exclude section simplifies the configuration but may affect the workflow's behavior on certain conditions. Ensure that the workflow still meets all requirements without this section.

---

Line range hint 1-30: Verify the impact of removing the TEMPLATE environment variable.

The removal of the TEMPLATE environment variable simplifies the configuration but may affect the workflow's behavior. Ensure that the workflow still meets all requirements without this variable.

e2e/extractor_template.spec.ts (3)

9-11: LGTM!

The introduction of the templateFramework constant improves configurability.

---

12-14: LGTM!

The introduction of the dataSource constant improves configurability.

---

17-21: LGTM!

The expanded conditional statement enhances control flow by adding more nuanced conditions.

e2e/streaming_template.spec.ts (3)

Line range hint 1-30: Verify the impact of removing the templateType variable.

The removal of the templateType variable simplifies the configuration but may reduce flexibility. Ensure that the test suite still meets all requirements without this variable.

---

Line range hint 1-30: Verify the impact of hardcoding "streaming" in the call to runCreateLlama.

Hardcoding the string "streaming" simplifies the configuration but may reduce flexibility. Ensure that the test suite still meets all requirements with this change.

---

29-119: LGTM!

The streamlined structure enhances readability and maintainability.