Spryker Community

Hi all,

What does testing mode mean in `docker/sdk` so what does it change to run `docker/sdk -t`

Thanks

<https://github.com/spryker/docker-sdk/blob/master/docs/02-development/06-running-tests.md>

Alike vagrant devvm, there is no separate DB\separate install recipe.

how is

docker/sdk -t

differnet from

docker/sdk testing

if they are different :slightly_smiling_face:

Is `docker/sdk -t` valid? I'm not sure. :slightly_smiling_face:

Or did you mean `docker/sdk cli -t` vs `docker/sdk testing`?

That I'm not sure I can answer. IMO they are similar but I may be wrong.

also one more thing … when I am using `-t` does it use different `config_*.php` ? or does it still use the same `config_default-docker.dev.php` 

Ah, there is a difference.
<https://github.com/spryker/docker-sdk/pull/261/files>
```docker/sdk cli -t - only runs cli in “testing mode”, but doesn’t start webdriver/removes scheduler. So docker/sdk cli -t it’s not the same as docker/sdk testing as I thought in the beginning.```

because when I start `cli` using `-t` it prints that environment is `<http://docker.dev|docker.dev>` so it seems to me like it still in the same env

then in this case `docker/sdk testing`  will be using a different config?

There is no other docker.* config, no? :slightly_smiling_face: It's dev\demo\ci only.

There are three - <https://github.com/spryker-shop/b2c-demo-shop/tree/master/config/Shared>

But depends on the project ofc. If you don't need other two...

we only use docker for dev mode basically