Hi,
thanks that's helpful for running the exact test I'm developing at the
moment, however I regularly want to check the whole module for
unintended changes, so I'm still looking for a way to run more than one
test and less than all. If I change something in the Javascript editor
module I want to make sure that I don't break something in another
class, however I can skip the tests for C++ locally since it's unlikely
that I break something and there's the CI safeguard which runs them
anyway. I think that's a common development workflow.
Do you use a mocking framework? I see that a lot of data and references
are created with utility classes which is a good approach for the test
cases in integration style. However, I also see cases where mocks would
be advantageous in terms of clearness and maintainability. There's quite
a lot of catching exceptions and returning early, so verification is
also necessary in unit tests (it's rarely the right approach in testing,
but in these cases it is).
Do you have any measurement, maybe even visualization of coverage?
-Kalle
Am 08.10.21 um 15:27 schrieb Michael Bien:
once you have build netbeans as described in the readme, you can simply
run individual tests via right click on the junit file after you opened
the module in netbeans.
you can also rebuild individual modules or run your netbeans build
directly from the IDE - you usually don't have to rebuild everything all
the time, or test everything (tests can take *very* long).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
