Articles

How to Save Money, Time, and More With Test Environment Management Tools

,

Companies today are becoming more and more application-driven, which in turn is making every company today a software company – whether they know it yet or not. With this, companies are having to issue more application releases than ever before, and their software delivery cycles are increasingly complex. Therefore, in order to cope with the number of applications they are supporting, large enterprises now need hundreds and sometimes thousands of test environments. But as the number of environments continues to rise, successfully managing them all is becoming more and more challenging by the day.

A recent survey conducted by Enterprise Management Associates (EMA), titled the EMA 2018 Test Environment Management Survey, found that only 4% of large enterprises have fully integrated test environment management (TEM) processes in the DNA of their application development, despite the overarching benefits that TEM tools can bring to businesses across a range of industries. Given the speed and efficiency improvements that TEM tools provide, the question should be asked, why aren’t more businesses integrating them effectively or even at all?

Source de l’article sur DZONE

/0 Commentaires/par

Domain-Driven Design in JavaScript

,

I wouldn’t class myself as a JavaScript developer, I always joke that it’s a language I never meant to learn. It’s so pervasive now, it just happened. I go through phases of enjoying it and despising it. But through the peaks and troughs of love and not quite hate. One problem persisted: if I’m to be a good JS developer and write functional JavaScript, how then do I write code in a way that implies a proper domain model?

In traditional OO languages, such as Java, C#, and even Go actually, it’s easy to write code that’s architected around a domain design. You have classes, which are big and do a lot of stuff. Which of course is something you generally avoid like the plague in JavaScript, for fair enough reasons.

Source de l’article sur DZONE

/0 Commentaires/par

Sloppy QA and How to Shorten the QA Process

, ,

Our CEO recently gave an interview with the news website PC. Check out what he had to say:

Code Issues as a Result of Making the Wrong Tests: This AI Can Help

Eli Lopian, Typemock’s CEO, was very frustrated by the lengthy time it took to develop software due to issues with testing. Therefore, he found a solution together with a few other people and as a result founded his own company.


Source de l’article sur DZONE (AI)

/0 Commentaires/par

The Role of Managed Service Providers in Software Development

,

Managed service providers are becoming a growing influence in the business world. With high-speed internet widely available, and the proliferation of cloud services in general, attitudes towards the remote management of services have changed considerably in a relatively short space of time. Businesses across the spectrum are increasingly turning to managed service providers to take care of some, or all, of their IT needs.

Software developers are just one of the many business individuals that can benefit from managed service providers. Many IT teams are leveraging external expertise to expand and improve their own development processes. An outside perspective can add much-needed input for organizations who are keen to streamline and make continuous improvements to their technology value stream. So, while many businesses can be adequately catered to with non-specific IT service management, others, such as those in software development, require a custom solution and specialized approach.

Source de l’article sur DZONE

/0 Commentaires/par

Continuous, Incremental, Progressive Delivery: Pick Three

,

Software developers have spent the last decade talking about Continuous Delivery and the benefits of delivering working code as often as possible. But it turns out that’s only one part of the whole picture of software delivery. Modern teams actually have three distinct outcomes they are trying to achieve — a holy trinity of continuous, incremental, and progressive delivery. Each of these delivery practices can help your team move faster with less risk.

Continuous Delivery

Continuous Delivery is a set of practices that ensure your code is always in a deployable state. You accomplish this by increasing the frequency at which code is committed, built, tested, and deployed-steps that in the past only occurred at the end of a project when it was ‘code complete’.

Source de l’article sur DZONE

/0 Commentaires/par

5 Quick Wins for Securing Continuous Delivery

,

“DevOps is Agile on steroids — because Agile isn’t Agile enough.”

So says Jim Bird, the CTO for BiDS Trading, a trading platform for institutional investors. Jim continued, "DevOps teams can move really fast…maybe too fast? This is a significant challenge for operations and security. How do you identify and contain risks when decisions are being made quickly and often by self-managing delivery teams? CABs, annual pen tests, and periodic vulnerability assessment are quickly made irrelevant. How can you prove compliance when developers are pushing their own changes to production?"

Jim was presenting at the 2018 Nexus User Conference on Continuous Delivery. Pulling on his 20+ years of experience in development, operations, and security in highly regulated environments, Jim laid how and why Continuous Delivery reduces risk and how you can get some easy wins toward making it more secure.

Source de l’article sur DZONE

/0 Commentaires/par

The True Agile Is Value Delivery That Never Stops

,

Software can be shipped by deadlines. In that case, it has some value that does not grow over time. To make the app great, it must be continuously upgraded. This is what true Agile is about.

"The Definition of Done" is a complex problem for many software development companies. How do you know when there are enough features? Is it worth the time to implement a functionality nobody might ever use? How do you know if we develop a thing the end users will adore? Do we stop at MVP or should we continue to work on the product?

Source de l’article sur DZone (Agile)

/0 Commentaires/par

Women in DevOps: Tanu McCabe

,

Tanu McCabe’s expertise as a solutions architecture director at Capital One has enabled her to lend invaluable insights about her exciting adventure within the company’s digital journey. Since 2015, Capital One, one of the country’s largest banks, has championed a large-scale tech transformation. During an interview, Tanu reflected on her decision to join Capital One, her hopes for the future direction of the company, and how burnout brought her to a dream job in DevOps.McCabe’s job as a solution architect allows her to provide leadership and guidance that leverages the latest technological developments. As part of her job, Tanu positions the company on the best solution designs, projects, and company-wide initiatives.

How did you decide to come to Capital One?

Source de l’article sur DZONE

/0 Commentaires/par

The DevOps Phonetic Alphabet

,

How many times have you had to spell out your name to fellow colleagues and partners on the other side of the world, asked about the spelling of a new open source tool someone introduced you to, or tried to write down the latest DevOps buzzword everyone is using? 

Our guess is quite a lot. That’s why we put together the DevOps phonetic alphabet. Next time you have to spell something out, or you ask for the letters in a word, you will have your very own codeword index. Sure, there’s the NATO phonetic alphabet, but chances are developers will understand the word “QA” much quicker than “Quebec.” It’s also a quick way for developers to communicate with each other without others understanding (though, let’s face it, they rarely do anyway). 

Source de l’article sur DZONE

/0 Commentaires/par

Jenkins in a Nutshell

,

In many projects, the product development workflow has three main concerns: building, testing, and deployment. Each change to the code means something could accidentally go wrong, so in order to prevent this from happening developers adopt many strategies to diminish incidents and bugs. Jenkins, and other continuous integration (CI) tools are used together with a source version software (such as GIT) to test and quickly evaluate the updated code.

In this article, we will talk about Jenkins, applicable scenarios, and alternatives to automated testing, deployment, and delivering solutions.

Source de l’article sur DZONE

/0 Commentaires/par