diff options
author | jcampan@google.com <jcampan@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-08-04 23:28:47 +0000 |
---|---|---|
committer | jcampan@google.com <jcampan@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-08-04 23:28:47 +0000 |
commit | 4ae627586ecb6184c3b766fd5128709442b17360 (patch) | |
tree | 44726dd64ec639e8545b189c52f9bb6de1ecb818 /chrome/tools | |
parent | 41c2cd46aecd34eb258ed92b242ee86c333f06a8 (diff) | |
download | chromium_src-4ae627586ecb6184c3b766fd5128709442b17360.zip chromium_src-4ae627586ecb6184c3b766fd5128709442b17360.tar.gz chromium_src-4ae627586ecb6184c3b766fd5128709442b17360.tar.bz2 |
Another attempt at this CL.
I had to revert because it was somehow causing regressions on the page cycler and start-up tests.
(I suspect because I did add an IPC message not at the end of the message list)
TBR=beng
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@351 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/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, 11 insertions, 13 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. diff --git a/chrome/tools/automated_ui_test_tools/possible_actions.txt b/chrome/tools/automated_ui_test_tools/possible_actions.txt index 4e0345b..a7cf2ab 100644 --- a/chrome/tools/automated_ui_test_tools/possible_actions.txt +++ b/chrome/tools/automated_ui_test_tools/possible_actions.txt @@ -10,8 +10,6 @@ SelectNextTab SelectPrevTab ZoomPlus ZoomMinus -Sessions -Bookmarks History Downloads -Applications
\ No newline at end of file +Dialog |