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

UM9F81RCP

Hi all,

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

Thanks

Valerii Trots

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

Valerii Trots

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

UM9F81RCP

nice thanks

UM9F81RCP

another quesiton

UM9F81RCP

how is

docker/sdk -t

differnet from

docker/sdk testing

if they are different 🙂

Valerii Trots

Is docker/sdk -t valid? I'm not sure. 🙂

Valerii Trots

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

UM9F81RCP

oh sorry I meant
docker/sdk cli -t

Valerii Trots

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

UM9F81RCP

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

Valerii Trots

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.

UM9F81RCP

because when I start cli using -t it prints that environment is [docker.dev](http://docker.dev) so it seems to me like it still in the same env

UM9F81RCP

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

UM9F81RCP

🤔

Valerii Trots

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

UM9F81RCP

in my case I hve only one

UM9F81RCP

docker.dev

UM9F81RCP

should I add more?

UM9F81RCP

😅

Valerii Trots

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

Valerii Trots

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

UM9F81RCP

I dont think we need them in our case

UM9F81RCP

we only use docker for dev mode basically