Dear Musaffir, we built the SLA system with the idea that the performance goal should not change with the test itself.(Ex: I consider my Transaction 'Search' as Failed when above 15s, whatever the test and the load).

I understand it may lack some flexibility. We need to keep this in mind for our SLA evolution.

In the short term, you can tweaks things by playing with the SLA configuration files that are located in <project>/sla_profiles in a readable XML format. You can change the files easily before an automated test (make sure to preserve the uids).

This method allows you to:

• change the threshold from a test to another
• enable/disable each sla-threshold