sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #29633
[Bug 1400277] [NEW] [request] want to run some scripts in a row and report the result of each script
Public bug reported:
from related question comment #2
-----------------------------------------------------
Creating the structure of files, which can run the tests in an unittest queue, is not simple from scratch, especially if the user has to transfer parameters.
I suggest, it would be fine to have some little official archive of sikuli files with the simple sample of a queued test.
For example:
- start.sikuli hub script, receiving some general parameters from the command line, collecting the suite of tests with their own parameters, and running it with HTMLTestRunner;
- tempate.sikuli containing __init__ with parsing coming parameters , some setUp, and some tearDown
- test.sikuli containing __init__ procedure to process coming parameters, some simple test itself, and __name__=='__main__' block at the bottom, allowing to debug the test from Sikuli IDE when necessary.
This tiny archive would save huge time of people getting familiar with
Sikuli, because normally it's really difficult for testers to write this
object-oriented skeleton.
** Affects: sikuli
Importance: Medium
Assignee: RaiMan (raimund-hocke)
Status: In Progress
** Description changed:
- form related question comment #2 ()
+ from related question comment #2
-----------------------------------------------------
-
+
Creating the structure of files, which can run the tests in an unittest queue, is not simple from scratch, especially if the user has to transfer parameters.
I suggest, it would be fine to have some little official archive of sikuli files with the simple sample of a queued test.
For example:
- - start.sikuli hub script, receiving some general parameters from the command line, collecting the suite of tests with their own parameters, and running it with HTMLTestRunner;
- - tempate.sikuli containing __init__ with parsing coming parameters , some setUp, and some tearDown
- - test.sikuli containing __init__ procedure to process coming parameters, some simple test itself, and __name__=='__main__' block at the bottom, allowing to debug the test from Sikuli IDE when necessary.
+ - start.sikuli hub script, receiving some general parameters from the command line, collecting the suite of tests with their own parameters, and running it with HTMLTestRunner;
+ - tempate.sikuli containing __init__ with parsing coming parameters , some setUp, and some tearDown
+ - test.sikuli containing __init__ procedure to process coming parameters, some simple test itself, and __name__=='__main__' block at the bottom, allowing to debug the test from Sikuli IDE when necessary.
This tiny archive would save huge time of people getting familiar with
Sikuli, because normally it's really difficult for testers to write this
object-oriented skeleton.
** Changed in: sikuli
Status: New => In Progress
** Changed in: sikuli
Importance: Undecided => Medium
** Changed in: sikuli
Assignee: (unassigned) => RaiMan (raimund-hocke)
** Changed in: sikuli
Milestone: None => 1.2.0
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1400277
Title:
[request] want to run some scripts in a row and report the result of
each script
Status in Sikuli:
In Progress
Bug description:
from related question comment #2
-----------------------------------------------------
Creating the structure of files, which can run the tests in an unittest queue, is not simple from scratch, especially if the user has to transfer parameters.
I suggest, it would be fine to have some little official archive of sikuli files with the simple sample of a queued test.
For example:
- start.sikuli hub script, receiving some general parameters from the command line, collecting the suite of tests with their own parameters, and running it with HTMLTestRunner;
- tempate.sikuli containing __init__ with parsing coming parameters , some setUp, and some tearDown
- test.sikuli containing __init__ procedure to process coming parameters, some simple test itself, and __name__=='__main__' block at the bottom, allowing to debug the test from Sikuli IDE when necessary.
This tiny archive would save huge time of people getting familiar with
Sikuli, because normally it's really difficult for testers to write
this object-oriented skeleton.
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1400277/+subscriptions
Follow ups
References