You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@bahmutov Am trying to generate code coverage report for our single spa application by executing e2e which are in bdd cucumber format. But the source code is not getting instrumented.
When we start angular server locally, it will be listening to some port say https://localhost:3000. But to access our local server, we login to dev url and switch to local application instead directly accessing from localhost.
Also, ours is single spa application which constitute multiple repos to perform one complete end to end flow.
In this case, can anyone please guide us to instrument source code of local server from non localhost url and generate code coverage report by executing cypress e2e scripts which are in bdd cucumber format
Cypress version 11.2.0
The text was updated successfully, but these errors were encountered:
@bahmutov Am trying to generate code coverage report for our single spa application by executing e2e which are in bdd cucumber format. But the source code is not getting instrumented.
Below is the project structure.
Root -> src-> FE code
Root -> cypress -> cypress scripts
When we start angular server locally, it will be listening to some port say https://localhost:3000. But to access our local server, we login to dev url and switch to local application instead directly accessing from localhost.
Open https://dev.domain.com/appname
then after login, update url to
https://dev.domain.com/local-appname to access application in local mode
Also, ours is single spa application which constitute multiple repos to perform one complete end to end flow.
In this case, can anyone please guide us to instrument source code of local server from non localhost url and generate code coverage report by executing cypress e2e scripts which are in bdd cucumber format
Cypress version 11.2.0
The text was updated successfully, but these errors were encountered: