Thanks for any input on that 👋

Oh goodness. You have a very hard problem 🙂

I have built the exact thing you're talking about. It's pretty difficult.

So... maybe

If you have the application code, I think I could help you test it. It might be possible but it depends on how the map is implemented.

If your map is canvas, you might have a hard time. If it's DOM nodes... I think you will be able to do it

Well I am not part of the project anymore. We were only part of a team for a limited amount of time. I just saw your great talk on vueconf and this case popped back into mind. So I don't have to test it, but thought maybe this is the right place to ask such a question. Just to have a few recipes for the next time I might stumble upon such a case.

Thanks a lot for your offer though 🙂

If you have a few hints where to start and what you would do in such a case, that would be of great value already.

(I had DOM nodes, I believe)

Yeah, I mean, I would literally just try to interact with the component

assert that things were "visible"

Cypress has a lot of those assertions already built in.

Ok. I see. So you would kind of just check the things I wrote down: e.g.: If I click on an item on the map -> will already expanded items within the list close and the clicked one expands? you would click on a map item (with cypress of course, e.g. by emitting a click event?) and then assert something like -> select the item in the list (maybe via id) and then check if it has a class

.is-expanded

. Would that kind of the right approach? Sorry for the noob question, but I don't have a lot of testing experience... 😅 and this would mean that I have to mount all the components within the same test environment... right?

You've got it exactly right @User

.click()

on the element 🙂 and then

.get('[data-testid=my-pin])

to figure out what's going on with the pin

ok perfect. Thanks for the input! Much appreciated!

Morning ✨

What do you recommend me to do in these cases? It comes out with many of the tests

Morning! We need a reproduction of the issue. Can you open a GH issue with steps to reproduce the failure?

Hello! I see that generally a proxy is set via ENV -- however, is it possible to dynamically use one on a spec-by-spec basis?

@full-jordan-99342 what do you mean

?

You can modify .env dynamically https://docs.cypress.io/api/cypress-api/env#Syntax

without an env file.

A general rule with Cypress is "anything that can be set inside of cypress.json is also available for modification at runtime"

I have a number of specs i want to run, but some of them i want to run with a proxy enabled, and some i don't (it's our hacky way to simulate traffic from another region)

(That's a brilliant solution, btw)

Let me know if Cypress.env will solve your issue

i'll give it a shot! thanks!