Test Hours

---

Each of a customer's workspaces draws from the test hours allocated by their subscription. Subscriptions have monthly terms and roll over on the same day each month. Unused hours do not accrue when subscriptions roll over. Test hours and subscriptions are managed on the Manage Hours page in the Errthquake portal.

Subscription Plans

Free Plan

• Maximum 2 minutes per test
• 20 minutes of test time per month
• Maximum 40 virtual users

Developer Plan

• Maximum 2 hours per test
• 16 hours of test time per month
• Maximum 1000 virtual users

Subscription Terms

Subscription months have a 30 day minimum -- if a calendar month does not have 30 days between rollover dates, the subscription will be extended until 30 days pass.

Subscriptions canceled mid-term stay active until their pending rollover date, then expire instead of rolling over.

Subscriptions purchased in the middle of another subscription term start a new subscription term with its rollover date at least 30 days from the purchase date.

Workspace Hours

A customer may have multiple Errthquake workspaces. All customer workspaces draw test time from the customer's bucket of test hours.

The Workspace Overview page in the Errthquake portal displays a chart showing the test time available, test time spent, and time allocated to tests in progress.

The Manage Hours page in the Errthquake portal shows the detailed status of the customer's test hours, including the subscription rollover date and a link to change the subscription plan.

Tracking Hours

When load tests are submitted for execution, the estimated test duration is allocated to test time in progress and held until the test is complete. When the test is complete its time in progress is returned to the customer's hours and its actual duration is taken from the customer's hours.

Tests estimated to run significantly longer than remaining test time are not executed, instead an informational message is displayed explaining this.

Estimating Test Time

• Duration tests are simply estimated to spend the submitted test duration.
• Benchmark tests are estimated by the expected command sequence duration, the number of CSV test input entries, and the requested number of simultaneous virtual users.
• Interactive tests are estimated like benchmark tests even though they run until explicitly stopped. If an interactive tests runs significantly longer than a customer's remaining hours, it may be stopped automatically.