| 2013-04-18 09:33:00 |
Dmitry Bolshakov |
bug |
|
|
added bug |
| 2013-04-18 11:30:00 |
RaiMan |
sikuli: status |
New |
Fix Committed |
|
| 2013-04-18 11:30:06 |
RaiMan |
sikuli: importance |
Undecided |
High |
|
| 2013-04-18 11:30:10 |
RaiMan |
sikuli: assignee |
|
RaiMan (raimund-hocke) |
|
| 2013-04-18 11:30:15 |
RaiMan |
sikuli: milestone |
|
x1.0 |
|
| 2013-05-07 14:03:44 |
RaiMan |
sikuli: importance |
High |
Medium |
|
| 2013-05-14 11:30:30 |
RaiMan |
sikuli: importance |
Medium |
High |
|
| 2013-05-14 11:30:40 |
RaiMan |
sikuli: milestone |
x1.0 |
x1.1 |
|
| 2013-06-09 16:58:07 |
RaiMan |
tags |
|
fkt-general |
|
| 2013-07-16 16:39:15 |
RaiMan |
sikuli: importance |
High |
Critical |
|
| 2013-07-16 16:39:53 |
RaiMan |
description |
I think it would be useful for tests with "wait" calls
(eg installation wizards can have long running dialogs "downloading" or "copying" etc) |
--- fixed with 1.0.1: Settings.LogTime=True
I think it would be useful for tests with "wait" calls
(eg installation wizards can have long running dialogs "downloading" or "copying" etc) |
|
| 2013-07-16 16:41:09 |
RaiMan |
description |
--- fixed with 1.0.1: Settings.LogTime=True
I think it would be useful for tests with "wait" calls
(eg installation wizards can have long running dialogs "downloading" or "copying" etc) |
--- fixed with 1.0.1: Settings.LogTime=True:
[info (16.07.13 18:40:37)] Exit code: 0
I think it would be useful for tests with "wait" calls
(eg installation wizards can have long running dialogs "downloading" or "copying" etc) |
|
| 2013-08-14 13:49:13 |
RaiMan |
summary |
[request] print timestamp in log messages |
[1.0.1 ok] [request] print timestamp in log messages |
|
