Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Project Overview

We have built two PoCs that works together:

  • The 1st PoC has funtions to serve static assets for the HTML/JS application (viewer, invite, upload), and send SMS with bit.ly link via twilio
  • The 2nd PoC is a simply PUT/GET matcher

Contest Objective

The goal of this competition is to develop an Advanced Test Plan to load test the PUT/GET matcher. Note we don't need to test the 1st PoC, but just the matcher.

JMeter is an option but please feel free to use any other tools or even scripts you write yourself as long as it works and yields good results e.g. PUT/GET performance while getting regular flow of HEAD requests.

The competitors in this competition are expected to provide the following deliverables.

  1. A document describing how to run, modify the test plan you created in Microsoft Word compatible document.
  2. JMeter project file (*.jmx) / Scripts / or any standard files needed for the testing if you choose to use other tools
  3. Graph Results collected by the Listener

Note: we want to make the tests as reusable as possible, i.e. independent of what technology we use to implement the PUT/GET/HEAD workflow currently implemented in the PoCs. So make sure you take this into account when implementing the tests.

Test Strategy

Following Thread Groups are required.

  1. test (low-volume - 1 user)
  2. benchmark (the average number of users - 10 users)
  3. load-test (the maximum number of users - 100 users)
  4. test destructively (1000 users)

Technologies

  • HTTP PUT/GET/HEAD

Provided Resources

We have provided instructions on how to test the PoCs manually in contest forum.



Final Submission Guidelines

Submission Deliverables

The competitors in this competition are expected to provide the following deliverables:  

  • A document describing how to run, modify the test plan you created in Microsoft Word compatible document.
  • JMeter project file (*.jmx) / Scripts / or any standard files needed for the testing if you choose to use other tools
  • Graph Results collected by the Listener

Final Submission

  • Your final submission must contain a single .zip file with all the submission deliverables.
  • For each member, the final submission should be uploaded to the Online Review Tool.
  • You must not include any identifying information, such as your handle, in your submission. Your submission should be anonymous and you will be scored down in screening for not complying.

ELIGIBLE EVENTS:

2014 TopCoder(R) Open

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30040487