• Post Reply Bookmark Topic Watch Topic
  • New Topic

Working with TDD Bitbucket and continues integration  RSS feed

 
Isaac Ferguson
Ranch Hand
Posts: 1063
3
Java Netbeans IDE Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I am working at the moment with Netbeans, TDD, Java and BitBucket. I just modified code and when there is any significative improvement I push it into BitBucket repo. I would like to add continues integration to the set of tools like Jenkins. I am new in the concept. Could it add some extra benefit? Why developers like to use it?
Or in other words which is the core benefit of it?

Regards, Isaac
 
Stephan van Hulst
Saloon Keeper
Posts: 7992
143
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The main benefit of continuous integration is that you have a system that is dedicated to testing your build, and warning all developers when a build doesn't pass unit tests. Sometimes developers may forget to test the build when they integrate their work, which may hamper the development process for other developers. Continuous integration aims to detect these breaks early.

For a one-man project, using CI probably isn't very useful, although you can go with one anyway, to get used to working with it for future projects with larger teams.
 
Isaac Ferguson
Ranch Hand
Posts: 1063
3
Java Netbeans IDE Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When working with TDD testing should be a problem, isnt it?

Because it is already tested when implemented
 
Stephan van Hulst
Saloon Keeper
Posts: 7992
143
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't understand what you mean.
 
Consider Paul's rocket mass heater.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!