Behat tests never end about fastest HOT 10 CLOSED

Issue solved.
We have some js generated and cached in some directory. Behat running under fastest couldn't access the directory. Running behat with sudo solved the issue.

bin/fastest "sudo bin/behat --profile=default {}"

from fastest.

Actually, still, that is not clear why fastest wasn't failing on this error?

 And I switch to the iframe "widget-preview"                                                                    # FeatureContext::iSwitchToIframe()
    And I wait for element "iframe[name=da-review-widget]" to appear                                               # FeatureContext::iWaitForElementToAppear()
      Element matching css "iframe[name=da-review-widget]" not found.

If it is not failing and running forever - it will be hell to debug.
Can I set some timeouts maybe somewhere in Behat config?

from fastest.

Maybe is JavaScript (ajax) issue?

from fastest.

Btw you can still set a timeout in the waitFor function

from fastest.

@DonCallisto we are using standard spin function approach as proposed in docs
http://docs.behat.org/en/v2.5/cookbook/using_spin_functions.html

I just run the suite with sudo, it still doesn't finish 2 last test. They could be any tests, as the order is random.

1	51/54	✔	23 s 365 ms	features/backend/some/1_builder.feature
1	52/54	✔	50 s 805 ms	features/backend/some/1_widget.feature

53 and 54 are running forever. no status returned.

Another issue: 1 feature from 54 failed at the beginning, but it continued running the rest. There should be a way to stop execution on the first fail.

from fastest.

I'm still not sure that's a fastest issue.
With this little code, no real examples, no way to test it, I can't help you at all.

from fastest.

@DonCallisto well, I'm using all standard configs, nothing special.
All configs as in fastest docs. I use provided helper for setting ENV and set ENV in GET and Cookie in FeatureContext in Behat, all works.
I use provided helper for changing DB name.
Then I have bash script to create DBs with expected names and load dump in them.
Config for Selenium and Hub with 2 nodes is standard, as in docs
https://github.com/SeleniumHQ/docker-selenium#version-2
I see all works in the console

I run tests with the command
find features/backend/ -name *.feature | sort -V -r | bin/fastest "bin/behat --profile=default {}" -p ${PROCESSES_NUMBER} -o --rerun-failed -vv
where PROCESSES_NUMBER = 2, for example.
I run 2 VNC sessions for both browsers and I see all works in parallel.

But I have 2 issues now.

1. When Behat run with fastest and faces Javascript error - it just stuck, never continues, never fail. This is not happening with normal Behat run.
2. If I run Behat as sudo in order to fix some permissions problems (just testing)
   then env ENV_TEST_CHANNEL_READABLE is not set and nothing pass as one DB used.

Have no idea why with normal Behat run all tests are green. And paralleled - some fail with JS errors.

Can it be that if 2 processes read the same JS file at the same time - the file is locked for another process?
For example, we have in Symfony routing.js to let JS use back-end routes. It loads on all pages. And I see errors like routing.js not found, but that's not true. :)

from fastest.

Again

With this little code, no real examples, no way to test it, I can't help you at all.

I use fastest in my projects and we have javascript scenarios too, so without code - or better, without a reproducible environment - we're not be able to help you more than this.

from fastest.

@seyfer did you resolved this issue?

from fastest.

@seyfer no I decided to not use it, unfortunately.

from fastest.