Documentation on API usage about lava-test-coverage HOT 4 CLOSED

Hi setting up modules can be time consuming only first time when all sources are to be assigned. Later on you just assign additions.

However I get you that keeping track of additions and doing it manually each time is not something desired.

I will create new tasks and do the required changes:

1. introduce api endpoints to do specific tasks if the current one can't be used for it (because were designed to work with this UI specifically)
2. create endpoint doc,swagger preferably

Hope this will help. Thanks for the feedback and let me know if this sounds good to you in terms of solving your problem.

from lava-test-coverage.

thank you for considering my feedback.

also there are still some few point that aren't clearly stated out in wiki / readme.

since at the start is i did plan to use lava for multiple project.
but after trying it i do start to think that lava is likely to be used for 1 project with multiple module in it.

which somewhat also not really suited for my case. where i am trying to achieve automation in gathering code coverage for multiple projects.

i'll submit another feedback through another issue for my difficulties above

from lava-test-coverage.

This could be achieved by running other instances of Lava but on different ports...just remember to update lava server port in Unity Lava helper c# class because it has default port hardcoded.
Anyway,support for multiple projects could be implemented. I'll report ticket for it.

from lava-test-coverage.

duplicate of #28
closing

from lava-test-coverage.