Variables from custom config files are not visible in test runners Settings > Configuration

Question

Variables from custom config files are not visible in test runners Settings > Configuration

mareru opened this issue 3 years ago · comments

When using this plugin as described, after opening test runner Settings tab > Configuration section, then I am able to see that config will be marked for properties that are set from custom config file qa.json, but on the other hand property baseUrl is null and not displaying the value from that file nor marking it in blue as filled from config (instead it says it is default).
Note that while running the test I can see that it is targeting baseUrl defined in qa.json. It is just not visible here in test runner.
I am not sure if this is cypress issue rather then this plugin issue.

Gleb Bahmutov · Answer 1 · Tue Jan 12 2021 07:22:32 GMT+0800 (China Standard Time)

Can you provide a repo showing the problem please?

…

Sent from my iPhone

On Jan 11, 2021, at 18:11, Marijana Rukavina ***@***.***> wrote: When using this plugin as described, after opening test runner Settings tab > Configuration section, then I am able to see that config will be marked for properties that are set from custom config file qa.json, but on the other hand property baseUrl is null and not displaying the value from that file nor marking it in blue as filled from config (instead it says it is default). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

Marijana Rukavina · Answer 2 · Tue Jan 12 2021 17:20:57 GMT+0800 (China Standard Time)

Here is the repo:
https://github.com/mareru/cypress-demo-issue
I noticed now that it doesn't even populates baseUrl while running test.
Maybe I am doing something wrong after all with the usage of the package ... I don't know

Gleb Bahmutov · Answer 3 · Tue Jan 12 2021 22:15:48 GMT+0800 (China Standard Time)

You accidentally put baseUrl into the env object, but it should be the top-level option, see https://github.com/bahmutov/cypress-extends#common-problems

Marijana Rukavina · Answer 4 · Tue Jan 12 2021 22:35:21 GMT+0800 (China Standard Time)

@bahmutov thanks for your reply but this didn't solve the problem
baseUrl is still null for some reason even when I put it on the top-level. I updated my code and pushed it.
When I run npm run smoke2 and test runner opens it is still as before baseUrl is null ...
Can you please help? :D

Gleb Bahmutov · Answer 5 · Tue Jan 12 2021 22:40:00 GMT+0800 (China Standard Time)

But now I do not see "extends" in your cypress.json file https://github.com/mareru/cypress-demo-issue/blob/main/cypress.json or in your "qa.json" file https://github.com/mareru/cypress-demo-issue/blob/main/qa.json

https://github.com/bahmutov/cypress-extends#use

Marijana Rukavina · Answer 6 · Tue Jan 12 2021 23:11:15 GMT+0800 (China Standard Time)

@bahmutov
Sorry, qa.json in the root of the project was legacy from some previous attempts.
The real one is in cypress/config/env https://github.com/mareru/cypress-demo-issue/blob/main/cypress/config/env/qa.json
It has the extends and it is still not working :(
Sorry once again for the confusion.

Gleb Bahmutov · Answer 7 · Wed Jan 13 2021 00:17:02 GMT+0800 (China Standard Time)

But you are not loading cypress/config/env/qa.json. You are loading qa.json from the current folder when running npm run smoke2

"smoke2": "cypress open --config-file qa.json ..."

Marijana Rukavina · Answer 8 · Wed Jan 13 2021 00:51:26 GMT+0800 (China Standard Time)

@bahmutov Thanks! That was the issue. Love you man :*