java - future proofing your code against changes in third party libraries -


How do we rely on our code against changes in third party libraries? Maintaining unit tests seems a way to go about it.

1) Configuration management to find out what versions of your libraries are required to build your build There are very few slopes to identify some distribution versions, so you might want to invest in a good version extractor, as well as compare the reports over time so that you can identify what has changed in your libraries. .

2) The phrase "unit test" is misused in the unit testing and integration test community. You need to check the spectrum of behavior in your configuration.

3) Managing interaction effects One of the most difficult issues for management is just upgrading one item. Often, the point of releases of libraries depend on the other point releases of other libraries. You can not take only one.

4) Planning for systematic upgrades. Make your project in schedule, work to test new releases so that you can guess the effects of upgrading. With that information, you can plan your upgrade for the time when you are not under the gun because it is too old or incompatible with the next supported JVM.


Comments

Popular posts from this blog

ios - How do I use CFArrayRef in Swift? -

eclipse plugin - Run java code error: Workspace is closed -

c - Error on building source code in VC 6 -