Dne 13. 05. 21 v 18:36 Laszlo Kishalmi napsal(a):
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.
- patch small changes during debugging using Debug | Apply Code Changes to patch the code immediately within the running application. Cannot change class structure/method signatures and has some other limitations. Use Debug | Stack > Pop topmost call to reexecute the changed method (though done for you in most cases).
- set Main Project to the module you're changing. Upon run, only that module (+ its necessary dependencies, if not built already) are compiled. Takes a few seconds + the time to boot the application.
- when chaning layer registrations, make Clean & Rebuild of the affected module. If you suspect something is stale in the running app, erase nbbuild/testuserdir/var/cache directory (or its part relevant to what you suspect was improperly cached).
... and when satisfied, write tests (if possible) to make sure you covered the corner cases too and ensure that the Travis shouts loud if someone breaks your new functionality in the future :)
-S. --------------------------------------------------------------------- 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
