diff options
author | jcampan@google.com <jcampan@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-08-04 20:40:50 +0000 |
---|---|---|
committer | jcampan@google.com <jcampan@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-08-04 20:40:50 +0000 |
commit | 719ead5027772e9be7708cb2414a95df5499595f (patch) | |
tree | ff679301ac868278c5479ff2d2d75b7175699540 /chrome/tools/automated_ui_test_tools | |
parent | c783216a001ae7885730700a7d3a6d7fcf4fba97 (diff) | |
download | chromium_src-719ead5027772e9be7708cb2414a95df5499595f.zip chromium_src-719ead5027772e9be7708cb2414a95df5499595f.tar.gz chromium_src-719ead5027772e9be7708cb2414a95df5499595f.tar.bz2 |
Reverting my last commit, it seems to cause regression on the page cycler tests.
TBR=beng
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@337 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/tools/automated_ui_test_tools')
-rw-r--r-- | chrome/tools/automated_ui_test_tools/README.txt | 20 | ||||
-rw-r--r-- | chrome/tools/automated_ui_test_tools/possible_actions.txt | 4 |
2 files changed, 13 insertions, 11 deletions
diff --git a/chrome/tools/automated_ui_test_tools/README.txt b/chrome/tools/automated_ui_test_tools/README.txt index e41d79c..22ff797 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-command 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-commands 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. +In the future we can write a script to parse automated_ui_test_report for failures and warnings.
\ No newline at end of file diff --git a/chrome/tools/automated_ui_test_tools/possible_actions.txt b/chrome/tools/automated_ui_test_tools/possible_actions.txt index a7cf2ab..4e0345b 100644 --- a/chrome/tools/automated_ui_test_tools/possible_actions.txt +++ b/chrome/tools/automated_ui_test_tools/possible_actions.txt @@ -10,6 +10,8 @@ SelectNextTab SelectPrevTab ZoomPlus ZoomMinus +Sessions +Bookmarks History Downloads -Dialog +Applications
\ No newline at end of file |