Application Development Exercises Software Software Review 
Leading Agile
JUNE 8, 2018
In Part 3 , we test-drove the initial thin vertical slice of our application. Now it’s time to complete the rest of the delivery pipeline: Continuous integration, static code analysis, and automated deployment. We did the application development work in Part 3. Step 9: Configure Static Code Analysis.
Project Accelerator News
AUGUST 18, 2023
When you’re carrying out due diligence and scoping out a share grab – that’s when you need to begin planning the IT side of a merger or takeover. The problem comes when a major issue develops with your routine operation and the support that previously underpinned it is deployed elsewhere. This stands to reason.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Leading Agile
JULY 4, 2018
Another cost to obtain more functionality is some limitation in what code can be supported. ZenTest and guard are specifically intended to support Ruby application development. Let’s set up guard to monitor a trivial Ruby application similar to the Python example we looked at before. group :test, :development do.
Leading Agile
OCTOBER 29, 2018
This may be an unfamiliar approach for readers who don’t come from an application development background. It’s one of the development skills that system administrators and infrastructure engineers are picking up from the software engineering world as devops gains ground in the industry.
Leading Agile
JUNE 7, 2018
In this installment, we’ll test-drive the first thin vertical slice of application functionality. Review the Story. We were just about to start test-driving our application. Let’s review our first Story before we proceed: blog-ci-cd-pipeline-cloud-3.html. Now we’re going to do software development work.
MPUG
MAY 6, 2021
You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. Kyle: Today’s session is eligible for one PMI, PDU in the technical category, and the code for claiming that with PMI is on the screen now.
Leading Agile
OCTOBER 22, 2018
In the 1960s, it was considered a baseline good practice in software engineering to test your code as you wrote it. The pioneers of software development in that era were proponents of various levels of testing; some advocated “unit” testing and some didn’t, but all recognized the importance of testing code.
Expert insights. Personalized for you.
69 
Let's personalize your content