At the moment the Trial terminology from RFC2544 is not used correctly within the test framework.

In the framework a trial is synonymous with a test, this needs to be fixed.
Definition of Trials and tests in RFC2544: "A particular test consists of multiple trials. Each trial returns one piece of information, for example the loss rate at a particular input frame rate."

During analysis it has been found, that some of the traffic generators already support a 'trial' in RFC2544 meaning. There was a discussion about this topic on meeting 3rd of August (https://wiki.opnfv.org/display/meetings/Vsperf). It was decided to keep configurable only the number of tests. The number of trials should not be configurable by user. Implementations of traffic generator classes should ensure correct behavior in case that minimal/exact/etc number of trials is defined by RFC.

Table with mapping between RFC2544 and traffic generators terminology, with highlighted features supported in Colorado:

At the moment in the framework, in the traffic gens the following functions:
send_rfc2544_throughput(self, traffic=None, trials=3, duration=20, ...)
start_rfc2544_throughput(self, traffic=None, trials=3, duration=20, ...)
send_rfc2544_back2back(self, traffic=None, trials=1, duration=20, ...)
start_rfc2544_back2back(self, traffic=None, trials=1, duration=20, ...)

need to be updated to use the test terminology instead of the trial terminology

The following files also need to be updated:
vsperf
conf/03_traffic.conf
core/traffic_controller_rfc2544.py
docs/configguide/trafficgen.rst
docs/requirements/vswitchperf_ltd.rst
docs/msc/traffic_controller.msc
docs/design/vswitchperf_design.rst
docs/design/trafficgen_integration_guide.rst
docs/userguide/yardstick.rst