© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The -v option in autopilot run should print logged messages, but not too many. Currently, with -v everything in debug is printed, which is too much. For example, when making a finger move, we get:
[...]
19:54:21.865 DEBUG _uinput:414 - Moving pointing 'finger' to position 270,116.
19:54:21.866 DEBUG _uinput:419 - The pointing 'finger' is now at position 270,116.
19:54:21.878 DEBUG _uinput:414 - Moving pointing 'finger' to position 270,110.
19:54:21.880 DEBUG _uinput:419 - The pointing 'finger' is now at position 270,110.
19:54:21.891 DEBUG _uinput:414 - Moving pointing 'finger' to position 270,104.
19:54:21.893 DEBUG _uinput:419 - The pointing 'finger' is now at position 270,104.
[...]
That's one line per pixel.
I think that -v should only print the info logging level. That way the test writer decides what goes into the -v log, and we can use it to put information about the high level user actions that the test executes, like "drag from the bottom", instead of the many finger moves.
Then, -vv should be the current -v, printing also the debug level in case we need extra information.
And we can add a -vvv to be the new -vv.