Welcome to the IBM Castle - JMeter Docker Load Testing Part 1 Challenge!

In a previous challenge we created a basic JMeter test plan against IBM Castle API and configured a Docker image to execute it.

The goal of this challenge is to extend the test plan to add more stress and load testing plans to the API and cover more endpoints.

Challenge Requirements

API Endpoints

The API endpoints definition are provided in challenge forums

• - All domino api endpoints are in scope.

Testing Strategy

Load tests can be used to uncover bottlenecks and lead to increased performance. Load tests can also be used to estimate optimum server load aka capacity planning.

You are provided with a document from winning submission in the past challenge, it is discussing a testing strategy plan with some assumptions. It gives you a good start to map out your test plan strategy.

Test Data

As in the provided winning submission, we are using csv files to configure test data, you will follow same approach and extend it to cover users, attachments, and any other test data needed.

All test data should test edge cases like large size attachments, or long messages .. etc.

JMeter Requirements

You need to implement different thread groups when testing the api endpoints :

• - Low volume test thread (1 user)

• - Benchmark test thread (12 users)

Your solution should be easily expanded to cover load/distructive load testing (100-1000 users), so please write your tests with that in mind.

Docker

Your test plans should run through Docker, if there are any changes needed to the Docker, you will need to fix it in this challenge and include it in your submission.

Deliverable

• - JMeter Test Plans files

• - JMeter Test Results files.

• - Updated Docker file (if needed)

• - Deployment document and verification. It should discuss your test strategy and any limitation to your test scenarios.

 

Final Submission Guidelines

.