Github user dragon512 commented on a diff in the pull request:

    https://github.com/apache/trafficserver/pull/1465#discussion_r103950549
  
    --- Diff: tests/getting_started.md ---
    @@ -0,0 +1,197 @@
    +
    +# Getting Started
    +
    +This directory contains different tests for Apache Trafficserver. It is 
recommended that all test move to this common area under the correct location 
based on the type of test being added.
    +
    +## Layout
    +The current layout is:
    +
    +**gold_tests/** - contains all the TSQA v4 based tests that run on the 
Reusable Gold Testing System (AuTest)
    +**tools/** - contain programs used to help with testing. 
    +
    +In the future a directory called **"unit/"** will be added for adding unit 
tests based on some standardized testing system.
    +
    +
    +## Scripts
    +
    +To help with easy running of the tests, there is a autest.sh and 
bootstrap.py file.
    +
    +### autest.sh
    +This file is a simple wrapper that will call the AuTest program in a 
python virtualenv. If the virtualenv is not setup it will try to install 
system. That will set up the Reusable Gold Testing System on most systems in a 
Python virtual environment. The wrapper add some basic options to the command 
to point to the location of the tests. Add --help for more details on options 
for running autest test system.
    +
    +### bootstrap.py
    +This script should try to install python35 or better on the system, and 
needed python packages for running the tests.
    +
    +# Advance setup
    +
    +AuTest can be install manually instead of using the wrapper script. The 
advange of this is that it is often easier to debug issues with the testing 
system, or the tests. There are two ways this can be done.
    +1. run the bootstrap script then source the path with a "source 
/env-test/bin/activate" command. At this point autest command should run 
without the wrapper script
    --- End diff --
    
    no typo.. it is in ./env-test. I will correct


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to