skills/load-testing-java/SKILL.md
Load test Java Spring Boot APIs using Gatling (JVM-native) and k6. Covers simulation design, feeders, assertions, Gradle/Maven plugin integration, and CI/CD pipelines. Use when: writing load tests in Java/Scala with Gatling, testing Spring Boot endpoints under load, integrating Gatling into Maven or Gradle builds, or comparing Gatling vs k6 for a Java project.
npx skillsauth add congiuluc/my-awesome-copilot load-testing-javaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
load-testing skill)| Criteria | Gatling | k6 | |----------|---------|-----| | Language | Java / Scala / Kotlin | JavaScript | | Best for | JVM teams, data-driven | Cross-team, CI/CD gates | | Protocol | HTTP, WebSocket, JMS, MQTT | HTTP, WebSocket, gRPC | | Build integration | Maven/Gradle plugin | CLI / GitHub Action | | Reports | Rich HTML (built-in) | Console, JSON, Prometheus | | Data feeds | CSV, JSON, JDBC, custom | SharedArray, JSON |
Recommendation: Use Gatling for JVM teams that want IDE-integrated, data-driven load tests with rich HTML reports. Use k6 for quick CI/CD pipeline smoke tests.
mvn gatling:test or gradle gatlingRunload-testing skill)target/gatling/ or build/reports/gatling/<dependencies>
<dependency>
<groupId>io.gatling.highcharts</groupId>
<artifactId>gatling-charts-highcharts</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>io.gatling</groupId>
<artifactId>gatling-test-framework</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>io.gatling</groupId>
<artifactId>gatling-maven-plugin</artifactId>
</plugin>
</plugins>
</build>
plugins {
id 'io.gatling.gradle' version '3.12.0'
}
dependencies {
gatling 'io.gatling.highcharts:gatling-charts-highcharts'
}
src/
gatling/
java/
simulations/
ProductSimulation.java # Product API simulation
AuthSimulation.java # Auth flow simulation
resources/
feeders/
products.csv # Test data
gatling.conf # Gatling configuration
logback-test.xml # Logging config
tools
Build VS Code extensions with TypeScript. Covers extension anatomy, activation events, commands, tree views, webview panels, language features, testing, and publishing. Use when: creating a new VS Code extension, adding commands/views/providers, building webview UIs, implementing language server features, testing extensions, or packaging for the marketplace.
development
Track implementations, features, bugs, and releases in a versioning document. Use when: adding a commit, completing a feature, fixing a bug, or preparing a release. Automatically updates CHANGELOG.md following Keep a Changelog format and Semantic Versioning.
development
Write frontend tests using Vitest and React Testing Library. Use when: testing React components, hooks, user interactions, form submissions, accessibility assertions, or mocking API services.
development
Write Angular frontend tests using Jasmine, Karma, and Angular TestBed. Use when: testing Angular components, services, pipes, directives, user interactions, form submissions, accessibility assertions, or mocking HTTP services.