github.com/shashidharatd/test-infra@v0.0.0-20171006011030-71304e1ca560/scenarios/README.md (about)

     1  # Test scenarios
     2  
     3  Place scripts to run test scenarios inside this location.
     4  
     5  Test jobs are composed of two things:
     6  1) A scenario to test
     7  2) Configuration options for the scenario.
     8  
     9  Three example scenarios are:
    10  
    11  * Unit tests
    12  * Node e2e tests
    13  * e2e tests
    14  
    15  Example configurations are:
    16  
    17  * Parallel tests on gce
    18  * Build all platforms
    19  
    20  The assumption is that each scenario will be called a variety of times with
    21  different configuration options. For example at the time of this writing there
    22  are over 300 e2e jobs, each run with a slightly different set of options.
    23  
    24  ## Contract
    25  
    26  The scenario assumes the calling process (bootstrap.py) has setup all
    27  prerequisites, such as checking out the right repository, setting pwd,
    28  activating service accounts, etc.
    29  
    30  The scenario also assumes that the calling process will handle all post-job
    31  works, such as recording log output, copying logs to gcs, etc.
    32  
    33  The scenario should exit 0 if and only on success.
    34  
    35  The calling process can configure the scenario by calling the scenario
    36  with different arguments. For example: `kubernetes\_build.py --fast`
    37  configures the scenario to do a fast build (one platform) and/or
    38  `kubernetes\_build.py --federation=random-project` configures the scenario
    39  to do a federation build using the random-project.
    40  
    41  Call the scenario with `-h` to see configuration options.