article thumbnail

AoAD2 Practice: Continuous Integration

James Shore

Continuous Integration. Most software development efforts have a hidden delay between when the team says “we’re done” and when the software is actually ready to release. Continuous integration is a better approach. Teams using continuous integration keep everyone’s code working together and ready to release.

article thumbnail

Automated testing with continuous integration for Electron applications

CircleCI

over native desktop software development methods, Electron.js has established itself as a trustworthy framework for developing desktop applications. In this tutorial, I will demonstrate how to test Electron.js apps and take that a step further by automating our testing process. Automating our tests.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Agile Book Club: Evolutionary Design

James Shore

Kent is the creator of Extreme Programming, the groundbreaking Agile method that introduced evolutionary design, test-driven development, continuous integration, and many other Agile practices to the world. It’s the basis of most of the material in The Art of Agile Development.

Agile 121
article thumbnail

My Best Essays

James Shore

The Art of Agile Development (Book) - 2008. The Agile how-to guide. Continuous Integration on a Dollar a Day - 27 Feb, 2006. An easier, cheaper (and better) way to do continuous integration. Testing Without Mocks: A Pattern Language - 27 Apr, 2018. Test-driven development in a nutshell.

article thumbnail

My Best Essays

James Shore

The Art of Agile Development (Book) - 2008. The Agile how-to guide. Continuous Integration on a Dollar a Day - 27 Feb, 2006. An easier, cheaper (and better) way to do continuous integration. Testing Without Mocks: A Pattern Language - 27 Apr, 2018. Test-driven development in a nutshell.

article thumbnail

AoAD2 Practice: Refactoring

James Shore

How to Refactor. Test-Driven Development. Technically, you can refactor at any time, but unless your IDE has provably-safe refactorings, it’s best to do it when you have a good suite of tests that are all passing. for instructions about how to run the build.). How often should we refactor? Constantly.

article thumbnail

Back to the Office With the Agile Fluency® Game

James Shore

Participants will play the game and learn how to apply its lessons to their real-world work. The game is focused on understanding the role software development practices play in a team’s success. As they play, participants will make choices about how to invest their time.

Games 64