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
Is your feature request related to a problem? Please describe.
It is currently possible to fetch code coverage report from the browser (the frontend code) as well as backend.
However, you can configure only 1 endpoint and if your application is composed of multiple services, we need to be able to extract code coverage from them as well.
Describe the solution you'd like
I want to configure cypress in such a way that it will collect code coverage from multiple endpoints, and remove expectBackendCoverageOnly which i think is redundant for example:
In order to provide backward compatability, still use the url property, and by default search for coverage from window.originUrl/__coverage__ remotePath and localPath are optional. We need this in case we are running our services on a remote machine / docker container and the paths are not synced with our local sources path.
Describe alternatives you've considered
You can basically create a service that doing the collection for you from all the other services, but its not a good approach.
Additionally, instead of remotePath and localPath you can create a middleware on your service that perform the mapping of the local source path, to what it should be in the docker host, but again it is not a good approach.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It is currently possible to fetch code coverage report from the browser (the frontend code) as well as backend.
However, you can configure only 1 endpoint and if your application is composed of multiple services, we need to be able to extract code coverage from them as well.
Describe the solution you'd like
I want to configure cypress in such a way that it will collect code coverage from multiple endpoints, and remove
expectBackendCoverageOnly
which i think is redundant for example:In order to provide backward compatability, still use the
url
property, and by default search for coverage fromwindow.originUrl/__coverage__
remotePath
andlocalPath
are optional. We need this in case we are running our services on a remote machine / docker container and the paths are not synced with our local sources path.Describe alternatives you've considered
You can basically create a service that doing the collection for you from all the other services, but its not a good approach.
Additionally, instead of
remotePath
andlocalPath
you can create a middleware on your service that perform the mapping of the local source path, to what it should be in the docker host, but again it is not a good approach.The text was updated successfully, but these errors were encountered: