Different process use the same database

[pmartelletti]

Is it possible to change database for the different process (maybe hacking the profiles)? Because right now, with no further config, they all touch the same database and therefore, for example, same user is being inserted in the database, or the data is removed from one scenario and it is needed for an other one that is runned in other process?

Thanks a lot for your help!

[neochief]

Yeah, I feel your pain. To solve this exact problem you could specify a set of profiles to run with. Each profile could have different database connection settings.

[kolinko-ant]

@neochief hi. Could you point out how to set different db connections to different behat profiles. I tried to run tests in parallel according to you docs but tests were failed because of one common sqlite database. Thanks for the answer

[neochief]

Here's one of the ways to do it:

1. Set up several vhosts which point to the same document root, where your application is sitting.
2. In your application, make it so that it lists all possible vhosts and have separate databases for each. In other words, if you visit your app from vhost1.com, it should connect to DB1, and if you visit vhost2 it should connect to DB2 and so on.
3. Set up behat profiles in behat.yml which corresponds to your vhosts. Here's example:

default:
  extensions:
    shvetsgroup\ParallelRunner\Extension:
      profiles:
        - p1
        - p2
p1:
 context :
       parameters :
            vhost: vhost1.com
p2:
 context :
       parameters :
            vhost: vhost2.com

In your FeatureContext file use these variables to navigate to corresponding locations. Read here how to do it:
http://stackoverflow.com/questions/20879472/how-can-i-get-the-parameters-from-behat-yml-to-a-php-file

[kolinko-ant]

@neochief thanks i got it. Will try it

[seyfer]

@neochief then we parallel only by profile, not by every feature.
is it supported to parallel per feature?
I managed to run every feature in parallel with DB per process. But have some issues
Check liuggio/fastest#132