In order to have consistent profiles for testing, it has been suggested to define and store traffic profiles based on operator representative scenario.
We are managing the profiles in a common place (FuncTest git repo) as
The detailed plans on how the profiles will be used in projects may be project-specific and hosted in the project repos, e.g.
A key goal of traffic profiles and the related types of test use is that we promote consistency in how the profiles are defined, implemented by load test vendors, and run in the various test tools and labs. That will help ensure an “apples with apples” comparison when we consider results from these tests.
A note of caution: small modifications to combinations of packet sizes or proportions of total (IMIX) can have a profound affect on the results (which are usually bounded by the extremes of Fixed Packet size testing).
|Mobile traffic||AT&T||Bryan Sullivan|
A global guideline shall be provided referencing all the different profiles.
For each traffic profile, we may expect: * description of the profiles (e.g. nb packets/s of size X,Y ) * documentation (how to use/adapt the profile,..)
The description shall be provided in a simple format: txt? json? …
It shall give all the relevant information regarding the IP traffic generated by the scenario.
All the profiles shall be stored in the commons directory of the Functest git repo