I am trying to get GLORP into the pharo 2.0 image. I managed to load GLORP , PostgresV2 driver and then changed the GlorpDatabaseLoginResource default login params. After that, i started running the tests starting with PostgresV2 tests TestPGConnection in this i got 2 failures testFieldConverter2 and testFieldConverter3.
after i ran the GlorpTest. here i got only 353 out of 674 tests passed. Is this normal? I am running the test using the testRunner. Any idea where i could have taken a possible bad step?
Thanks in Advance.
I got all test correct now. The probelm was in the image i was checking the DateAndTime offset: method was modified somehow (may be installing some other packages did that). So that was causing my Date And time related functions to fail. After i loaded all to a fresh image and ran it was like a fine piece of cake. :)
Related
for my project I am using junit5 for testing. Now, as we know when we run test in parallel, all the logs get mixed in different order. Now, as my project is more of backend, it requires debugging of logs alott.
Thus , is there a way when we can reorder the logs on the basis of test method ran ? here anyone has faced such issue and resolved it OR have any thoughts on that. It would be much help. Thank you.
I am using IDEA 15 for a Play! 2 Application, but I am having problems that the compiler seems to get stuck. Generally when I change a file and save it compiles in a second and I can test. But often it gets 'stuck'.
No warning or message, but refreshing the page just keeps waiting.
And sample is one Scala template which took 43 seconds to compile, and often the only way to get back going is to restart the debug session, but that takes a few minutes as I sometimes have run a 'activator clean' and have to reload all my test data.
Is there a setting somewhere the I might have missed?
I use selenium 2 with Phpunit. when I run a script I got this error during the run.
PHPUnit_Extensions_Selenium2TestCase_NoSeleniumException: Error connection[28] to localhost:4444/wd/hub/session/edf323b4-c6ba-471a-9966-f2b9f3718084/url: Operation timed out after 60000 milliseconds with 0 bytes received
sometimes after several seconds and sometimes after 20+ minutes (memory: 48Mb ).
it takes a lot of time to execute the script. ( it go over like 100 news in different pages )
but I don't believe that it is a problem ( sometimes it crush after seconds ).
I already tried update the selenium and phpunit framework to last version but it doesn't helps.
Is there any option to continue the script after the connection crush?
or avoid the crush?
I know that I can try to increase connection time, but I look for a different solution or explanation why it happens. any ideas?
thanks.
the problems with connection is because the CURL, I tried to change the php.ini and increase the timeout but it not works so I understand that probably selenium set the timeout on the fly or something. after a short grep I found this file:
phpunit/phpunit-selenium/PHPUnit/Extensions/Selenium2TestCase/Driver.php
in the construct method it possible to change the default of the 'timeout' variable. to make sure that this parameter never changed ( if you lazy to find all the places where selenium calls to this class ) set your default timeout to the 'seleniumServerRequestsTimeout' property ( not recommended ).
I had the same issue and after days trying everything(I tried the solutions in this question too) without success to solve this issue, I decided to change the browser.
I downloaded the Chrome Driver and everything started to work without any problem.
Which leads me to believe that can be some version conflict or something else.
I used Selenium version 2.53.0 and PhantomJS version 2.1.1.
I encountered the same problem.
It was caused by accessing to sessions and using session_id(). You should use session_write_close() to fix the issue.
A few month ago i wrote some scripts to fetch the itunes connect sales reports automatically. Today i noticed that the scripts has stopped working correctly, so i searched for the problem.
Obviously the Autoingestion Tool from Apple (Autoingestion.class) has stopped to create the expected output files...
Usage Example:
java Autoingestion user *pw* vendor Sales Daily Summary 20130401
Syntax is still correct regarding http://www.apple.com/itunesnews/docs/AppStoreReportingInstructions.pdf
The tool runs fine without any errors. Just the expected output file is missing :(.
To except problems with java - i tested the tool on different platforms with different JVM versions.
Is anyone else experiencing this problem?
I had the same issue, but per your own comment, I tried it on another box with an up to date JRE, I believe, and it worked. (I'd tried it on my dev box, but running it on the live box worked. Makes sense.)
Just adding, this is the output we want to see:
$ java Autoingestion autoingestion.properties <vendor> Sales Daily Summary 20130801
S_D_<vendor>_20130801.txt.gz
File Downloaded Successfully
I'm inclined to think there should always be output from running Autoingestion. I actually had the wrong credentials when I ran it at first, but it couldn't even tell me that, in the wrong environment.
After quite a few hours of searching for answers to this to no avail, along with trying to source the issue myself within rubymine, I am now resigning to asking a question for it...
When I run one of my scenario's in my feature file, or all scenario's, it only processes the background steps and then ignores all the others that are within my scenario.
The stats at the end then report:
1 Scenario (1 Failed)
4 Steps (3 Skipped, 1 Passed)
So no steps failed! I have verified that the scenario works on another machine and passes successfully. Does anyone have an idea why it would just be ignoring my scenario steps?
Thank you in advance
I have actually managed to fix this problem myself!!! :)
In the javascript_emulation.rb file there is a known issue around capybara and racktest, the workaround and easy fix for that is to remove ::Driver after :Capybara for the java emulation bits.
If none of the ::Driver entries are removed the following error is returned:
undefined method 'click' for class 'Capybara::Driver:RackTest:Node' (NameError)
then a list of the problem areas in different files.
If the ::Driver entry is removed from the class Capybara::Driver:RackTest::Node
then the test will run but only process the background tests.
All instances of ::Driver must be removed in this file. For me there were 4 in total.
Hope this helps others :)