Just right click on the module you've changed and Test.
Of course it is as good as the tests are, also from time to time it is
worth to test all integrations / dependencies, so rebuild and test
everything, but most common we are using our CI (Travis/GitHub) to do
that when we create a branch/PR.
And then we have manually executed testcases for NetCat.
On 5/13/21 9:12 AM, Jeremy Cavanagh wrote:
Hi All,
First, I must apologise for asking such a question, but, I have
trawled the internet and not found an answer.
My background is not computer science (which I expect you've already
figured out) and so I have a big hole in my knowledge. However, I
would like to look at some things in the NetBeans sources that
interest/bug me.
What I need to know is how do you test any changed code? I can't
believe it is necessary to rebuild the app every time that would
surely take too long and possibly not very informative. For my system
it varies between 25 to 30 minutes. So when you change a
class/module/cluster what do you do to see if it works correctly or
needs more modifications.
Any guidance would be appreciated, especially, if it's in the right
direction.
Kind regards
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
