diff options
| author | jcampan@google.com <jcampan@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-08-04 19:59:31 +0000 |
|---|---|---|
| committer | jcampan@google.com <jcampan@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-08-04 19:59:31 +0000 |
| commit | 856ac4b39c729d184511244ebe0349e99e89879e (patch) | |
| tree | 20122d9151d1971918333ba8eb2df0c5eca4f139 /chrome/tools/automated_ui_test_tools/README.txt | |
| parent | b33452302702b3915e1110dae72fc8a746b3358c (diff) | |
| download | chromium_src-856ac4b39c729d184511244ebe0349e99e89879e.zip chromium_src-856ac4b39c729d184511244ebe0349e99e89879e.tar.gz chromium_src-856ac4b39c729d184511244ebe0349e99e89879e.tar.bz2 | |
Added testing of Chromium dialogs to the automated ui tests.
The new dialog command fires up a dialog (chosen randomly) and exercises it.
BUG=None
TEST=Run the automated_ui_test
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@333 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/tools/automated_ui_test_tools/README.txt')
| -rw-r--r-- | chrome/tools/automated_ui_test_tools/README.txt | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/chrome/tools/automated_ui_test_tools/README.txt b/chrome/tools/automated_ui_test_tools/README.txt index 22ff797..e41d79c 100644 --- a/chrome/tools/automated_ui_test_tools/README.txt +++ b/chrome/tools/automated_ui_test_tools/README.txt @@ -1,18 +1,18 @@ -auto_ui_test_input_generator.py takes in a list of possible actions separated by new lines, -the number of commands per file, and the number of actions per command, and generate either -a single random file or a number of files containing all possible commands. This file is then +auto_ui_test_input_generator.py takes in a list of possible actions separated by new lines, +the number of commands per file, and the number of actions per command, and generate either +a single random file or a number of files containing all possible commands. This file is then used as input to automated_ui_tests.exe (see chrome/test/automated_ui_tests/automated_ui_tests.cc/h) -which will run the commands, reporting on the success or failure of each. +which will run the commands, reporting on the success or failure of each. -An example of typical use: +An example of typical use: -$ python auto_ui_test_input_generator.py --action-list-file="possible_actions.txt" --output="automated_ui_tests.txt" --commands-per-file 100 --actions-per-commands 5 +$ python auto_ui_test_input_generator.py --action-list-file="possible_actions.txt" --output="automated_ui_tests.txt" --commands-per-file 100 --actions-per-command 5 $ automated_ui_tests.exe --input="automated_ui_tests.txt" --output="automated_ui_test_report.txt" -This will generate a random sequence of 100 commands containing 5 actions each and write it, formatted in XML, -to automated_ui_tests.txt. Then automated_ui_tests.exe reads that file, runs the commands, and outputs an XML -file to automated_ui_test_report.txt. +This will generate a random sequence of 100 commands containing 5 actions each and write it, formatted in XML, +to automated_ui_tests.txt. Then automated_ui_tests.exe reads that file, runs the commands, and outputs an XML +file to automated_ui_test_report.txt. -In the future we can write a script to parse automated_ui_test_report for failures and warnings.
\ No newline at end of file +In the future we can write a script to parse automated_ui_test_report for failures and warnings. |