🧪 Add E2E tests for Welcome View in Konveyor sidebar

[RanWurmbrand]

Summary

• Add end-to-end tests for the Welcome View component in the Konveyor VS Code extension sidebar
• Tests verify welcome message visibility, navigation links functionality, and documentation link presence

Test Coverage

• Welcome message visibility: Verifies the welcome content and greeting text appear in the sidebar
• Open Analysis Panel link: Tests that clicking the link opens the Analysis View webview
• Manage Profiles link: Tests that clicking the link opens the Manage Profiles view
• Documentation link: Verifies the documentation link text is present

Test Details

• Uses the coolstore test repository as the test fixture
• Tests are tagged with @tier3
• Includes proper setup/teardown with beforeAll and afterAll hooks

Summary by CodeRabbit

• Tests
  • Added an end-to-end test suite for the Welcome View: verifies sidebar welcome message, that the “Open Analysis Panel” and “Manage Profiles” links open their respective views and display expected content, checks for documentation text/link presence, runs against a sample repository for realistic validation, and ensures proper setup and teardown including closing the app after tests.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new end-to-end test suite at tests/e2e/tests/base/welcome-view.test.ts. The suite launches a test VSCode instance with a sample repository, asserts visibility of the Welcome sidebar message and documentation text/link, verifies that the “Open Analysis Panel” and “Manage Profiles” links open their respective views and display expected content, uses timeouts up to 30s for visibility checks, and closes the test app in teardown.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description includes comprehensive summary, test coverage details, and test details sections, but does not use the required PR title prefix format (should use 🌱 emoji alias per the template).	Update the PR title to use the standard 🌱 emoji alias instead of 🧪 to comply with the repository's versioning and release tooling standards.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title uses 🧪 emoji prefix (not the standard 🌱 for tests/infra), is clear and specific about adding E2E tests for Welcome View, and aligns with the actual changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[abrugaro]

Looks good overall, some considerations:

• Try not to use explicit timeouts, they explicitely increase the test time and most of the times they're not needed
• Test PRs titles should start with 🧪 , not 🌱
• Try not to hardcode "konveyor", that won't work with other brandings