Kubernetes is one of the fastest growing open source projects in history, and it's taking the DevOps world by storm. With so many resources being poured into this technology, it would be nice if there were some benefits for testing.
Tools like JIRA, Service Now for Incident management, I'm looking for a software platform that will keep track of all related documentation, test plans, user sign offs etc... But what I have not been able to find and is critical for me is a Parent - Child, Child - Child relationship of all changes.
A good branch-merge strategy facilitates processes among multiple developers and is the basis for any well-functioning DevOps pipeline that uses continuous integration. Let’s explore branching strategies, merging strategies, and how you can put them together in a way that’s right for your team in order to bring quality features to production faster.
DevOps teams struggle to ensure quality in multiple daily deployments. Traditional testing approaches have often failed in this context, but there are exciting new ways to test. Laurent Py and Vincent Prêtre will explain how, at Hiptest, DevOps teams combine behavior-driven development (BDD) techniques with business metrics analysis to continuously assert the quality of their product. BDD scenarios align teams to a common goal, and users provide feedback to ensure their needs are met. The team transforms usage scenarios into tests that enable developers to deliver the functionality expected, and product analytics are collected to ensure that the functionality is valuable to users. Analytics data is then used to learn how the new feature impacts the user experience. Laurent and Vincent will explain how this approach reduces siloed communication and combines scenarios and data in living documentation.
DevOps teams struggle to ensure quality in multiple daily deployments. Traditional testing approaches have often failed in this context, but there are exciting new ways to test. Laurent Py and Vincent Prêtre will explain how, at Hiptest, DevOps teams combine behavior-driven development...
Empathy is a technical skill. Don’t worry; you read that correctly. While empathy is often cited as a critical “soft skill,” it doesn’t stop there. Empathy is also an incredibly technical topic that is more accessible to analytical engineers—and more vital to building software—than you might think. Andrea Goulet, a noted expert on communication in the software industry, will debunk several myths around empathy, including that empathy is just a feeling, that technical folks can’t access empathy, and that empathy is just a high-level, touchy-feely fad. Andrea will demonstrate how empathy is a crucial skill for all developers of software, and she will give you practical and immediately actionable advice for making empathy a central focus of your daily software development communication practices. She'll also explore the place for empathy while you’re coding and testing.
In this interview, Michael Faulise, the founder and managing partner at tap|QA, explains how the move toward DevOps and away from release management is giving control back to developers, then details why major companies often need partners to leverage CI, CD, and other modern techniques.
Behavior-driven development (BDD) has been around for a while and is here to stay. However, the added abstraction levels pose a technical problem for writing and managing tests. While BDD does a great job of marrying the nontechnical aspect of test writing to the technical flow of an application under test, keeping this information under source control becomes problematic. Frameworks such as JBehave, Cucumber, or Robot give subject matter experts that additional ability to write tests, but they are often restricted access from them; because people treat test cases as code, they get stored in source control repositories. Additionally, these given-when-then steps soon can grow to an extent where they are difficult to manage without an IDE, and nontechnical people lose interest. Using management tools, Max Saperstone shows how to manage these nontechnical steps and keep them in sync with the automaton in tools such as Git.