-
Notifications
You must be signed in to change notification settings - Fork 1
Added Vanilla Java Sample Project #4
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds a new "vanilla Java" Selenium sample project to the browserstack-selenium-load-testing-sample repository, demonstrating how to run Selenium tests without a testing framework using just plain Java with a main method approach.
Key Changes:
- Added standalone Java test implementation using main method instead of test framework annotations
- Configured Maven build setup with Selenium 4.15.0 dependency
- Included BrowserStack Load Testing configuration and documentation
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| vanillajava/src/test/java/com/example/SimpleTest.java | Implements two Selenium test scenarios (add to cart, checkout flow) using plain Java with main method execution instead of test framework annotations |
| vanillajava/pom.xml | Maven configuration with Selenium dependencies, compiler settings for Java 11, and surefire plugin configuration |
| vanillajava/browserstack-load.yml | BrowserStack Load Testing configuration for Selenium with language and dependencies setup |
| vanillajava/README.md | Setup instructions including Maven installation, BrowserStack CLI download links, and test execution steps |
| README.md | Minor whitespace addition to the root README file |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| language: java | ||
|
|
||
| # Add list of file paths under 'dependencies' to help set up the test environment by installing required packages. Example: path to 'pom.xml' for Java projects using Maven, path to 'package.json' for Node.js projects. | ||
| # Add list of file paths under 'testConfigs' to define which configuration files should be used to run tests. Example: path to 'playwright.config.ts' for Playwright (Node.js), path to 'testng.xml' for Selenium (TestNG). | ||
| files: | ||
| dependencies: | ||
| - ./pom.xml | ||
| testConfigs: [] |
Copilot
AI
Dec 11, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The browserstack-load.yml configuration is missing the 'framework' field that is present in all other test framework examples (junit-4, junit-5, testng). For vanilla Java without a test framework, you should either add a framework field with an appropriate value (possibly 'none' or 'vanilla') or explicitly document why it's omitted. This inconsistency may cause confusion or issues with the BrowserStack Load Testing service.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
No description provided.