18 January 2026:
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
This forum is now archived and is in read-only mode. Please continue discussions on our improved new Sahi Pro Community forum.
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
Testrunner
****
* OS Name: Windows 7
* Browser Name: Chrome 16
* Sahi Build: V3.5
****
Hello!
I wrote 22 tests, so I decided to create my first suite file.
The test.suite was look like:
After that I executed start_sahi.bat and the testrunner.bat with the following parameters:
It finished so early, so I added
The result was that it only runs 10 files from 22.
1. What should I do if I want to run all the tests?
I modified testrunner to SINGLE_SESSION=true, but it doesn't get better.
The other strange thing was I got FAILURE, which I've never caught at the GUI, so I added custom onScriptFailure(), onScriptError() and onScriptEnd().
For example:
I've read the documentation about it, but 2 things aren't clear.
2. What should I do if I want logging why my test failed next to its name? (f.e.: Is there $error?)
3. What is different exactly between failure (only assert?) and error?
* OS Name: Windows 7
* Browser Name: Chrome 16
* Sahi Build: V3.5
****
Hello!
I wrote 22 tests, so I decided to create my first suite file.
The test.suite was look like:
First.sah
Second.sah
ThirdTest.sah
// etc...
After that I executed start_sahi.bat and the testrunner.bat with the following parameters:
testrunner test.suite http://www.example.hu chrome
It finished so early, so I added
_debugToFile(_scriptName() + ": start", "logs.txt");
to the beginning of the files to be sure about that every tests are executed.The result was that it only runs 10 files from 22.
1. What should I do if I want to run all the tests?
I modified testrunner to SINGLE_SESSION=true, but it doesn't get better.
The other strange thing was I got FAILURE, which I've never caught at the GUI, so I added custom onScriptFailure(), onScriptError() and onScriptEnd().
For example:
function onScriptFailure()
{
_debugToFile(_scriptName() + ": failure", "logs.txt");
}
I've read the documentation about it, but 2 things aren't clear.
2. What should I do if I want logging why my test failed next to its name? (f.e.: Is there $error?)
3. What is different exactly between failure (only assert?) and error?
Comments
First of all, there shouldnt be any issue running 22 scripts from the suite file.
You dont have to change SINGLE_SESSION=true.
Could you please click on Logs link and check which script is not executed? Try to run that particular script from the controller and check if it works fine.
Also, could you please check if you are getting any error on Sahi console? If so please post it here.
Also, kindly check if you are facing this issue with all other browsers.
Could you please check this link : http://sahi.co.in/w/sahi-call-back-functions
Regards
Sumitra
I recongised that it even fails at the first two tests, so I only played with them.
I created a new suite file: try.suite
[h]Single tests[/h]
First I opened my Chrome, and I got these results for Fooldal.sah and Kereses.sah:
1. Chrome: Sahi Controller The only strange thing was the "Script error. (:)".
In the logs it wrote "No trace available", but it showed Success at the end.
2. Chrome: Testrunner Everything worked fine.
After that I tried them with Firefox (9.0.1).
3. Firefox: Sahi Controller
4. Firefox: Testrunner Everything was the same like in Chrome. So if I tried them as single tests everything was OK.
[h]Suite files[/h] I could experience that it was succesfully with Kereses.sah, but it skipped the Fooldal.sah.
In the console of start_sahi I could only read that it kills Fooldal.sah.
Best wishes,
Claritas
Could you please post the script of Fooldal.sah here?
Also, check if you are getting any error in Logs? If so then please post it here.
Regards
Sumitra
Here is the source of Fooldal.sah: http://pastebin.com/xpCAqkTA
I hope it helps.
That's why I really don't know what is happening with it next to other testcases in a suite file. :S
I could reproduce the same. I m working on it, will let you know once i find the solution.
Also, i see that path to the log.txt should be given fully.
Regards
Sumitra
Thanks a lot, I'm waiting for the solution.
Good Luck!