test: run regression tests against localhost:8080/webapp

[jo-elimu]

Issue Number

• Resolves Run regression tests against localhost when a new pull request is created #2065

Purpose

• Run regression tests against the most recent changes in each pull request.

Technical Details

• Sleep 2 minutes before running tests, to give the Jetty server enough time to launch the webapp.

Testing Instructions

Screenshots

---

Format Checks

Note

Files in PRs are automatically checked for format violations with mvn spotless:check.

If this PR contains files with format violations, run mvn spotless:apply to fix them.

[coderabbitai]

Walkthrough

The pull request removes the "Regression Tests" section from the pull request template. This section previously contained specific commands to run backend and frontend regression tests locally. The update eliminates the guidance for reviewers to execute these tests manually when verifying pull request changes.

Changes

File(s)	Change Summary
.github/pull_request_template.md	Removed the "Regression Tests" section that contained commands for running backend and frontend tests.

Assessment against linked issues

Objective	Addressed	Explanation
Run regression tests on localhost when a PR is created [#2065]	❌	The PR removes instructions for local regression testing without implementing changes to run tests on localhost.

Suggested reviewers

• tomaszsmy
• vuriaval
• alexander-kuruvilla
• SnehaHS65

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c6d12c9 and b71863b.

⛔ Files ignored due to path filters (2)

• .github/workflows/maven-regression-test-rest.yml is excluded by !**/*.yml
• .github/workflows/maven-regression-test-ui.yml is excluded by !**/*.yml

📒 Files selected for processing (1)

• .github/pull_request_template.md (0 hunks)

💤 Files with no reviewable changes (1)

• .github/pull_request_template.md

⏰ Context from checks skipped due to timeout of 90000ms (8)

• GitHub Check: build (windows-latest, 21)
• GitHub Check: build (ubuntu-latest, 17)
• GitHub Check: build (macos-latest, 21)
• GitHub Check: build (macos-latest, 17)
• GitHub Check: build (windows-latest, 17)
• GitHub Check: build (ubuntu-latest, 21)
• GitHub Check: test_rest_ENG
• GitHub Check: test_ui

---

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

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 15.19%. Comparing base (e7df071) to head (0312c91).
Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##               main    #2067   +/-   ##
=========================================
  Coverage     15.19%   15.19%           
  Complexity      404      404           
=========================================
  Files           243      243           
  Lines          6672     6672           
  Branches        747      747           
=========================================
  Hits           1014     1014           
  Misses         5608     5608           
  Partials         50       50           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.