Hello and welcome, strong qu wrote: > If we plan to contribute changes to OpenOCD, is there a test suite we can > run trhough to verify our changes? Say if we implement ARMv8/AArch64 > support, how can we make sure the change won't break other device/platform?
This is a very good question, but unfortunately there exists no test suite for OpenOCD. The primary method used to avoid that new problems are introduced by mistake is peer review. One or several members in the community must review each change to the source before it is included in the project. This process takes longer than regression tests, but it is also more reliable. And it is possible to make review faster by creating small changes which are quick and easy to review. Naturally, as you point out, some structural changes will require larger changes, which means more work also for the reviewers, but this is anyway very welcome, because many parts of the OpenOCD code can certainly be improved. Please remember to separate each logical change into an individual commit. This helps speed up review, and helps future developers when studying the development history. Kind regards //Peter ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
