In this article, we will explore the concept of continuous delivery and its numerous benefits for modern software development.

The design principle of separation of concerns can be seen in action in this article, which presents a real-life example of MuleSoft.

Appropriate EA framework selection is critical for Enterprise Architects based on the Organization's needs and goals.

In this post, learn how to maintain a harmonious balance between driving Product Goals and nurturing professional relationships with your stakeholders.

The article presents a compiled list of unit tests naming strategy that one could follow for naming their unit tests. The article is intended to be a quick reference instead of going through multiple great pages such as following. That said, to know greater details, please feel free access one of these pages listed below and know for yourself. What are some popular naming conventions for unit tests? Unit Tests Naming Best Practices GivenWhenThen Technique How to Unit Test Stream Pipelines and Lambdas CI/CD Pipeline Testing Following are 7 popular unit tests naming conventions that are found to be used by majority of developers and compiled from above pages: MethodName_StateUnderTest_ExpectedBehavior: There are arguments against this strategy that if method names change as part of code refactoring than test name like this should also change or it becomes difficult to comprehend at a later stage. Following are some of the example: isAdult_AgeLessThan18_False withdrawMoney_InvalidAccount_ExceptionThrown admitStudent_MissingMandatoryFields_FailToAdmit MethodName_ExpectedBehavior_StateUnderTest: Slightly tweaked from above, but a section of developers also recommend using this naming technique. This technique also has the disadvantage that if method names get changed, it becomes difficult to comprehend at a later stage. Following is how tests in first example would read like if named using this technique: isAdult_False_AgeLessThan18 withdrawMoney_ThrowsException_IfAccountIsInvalid admitStudent_FailToAdmit_IfMandatoryFieldsAreMissing test[Feature being tested]: This one makes it easy to read the test as the feature to be tested is written as part of test name. Although, there are arguments that the “test” prefix is redundant. However, some sections of developer love to use this technique. Following is how the above tests would read like if named using this technique: testIsNotAnAdultIfAgeLessThan18 testFailToWithdrawMoneyIfAccountIsInvalid testStudentIsNotAdmittedIfMandatoryFieldsAreMissing Feature to be tested: Many suggest that it is better to simply write the feature to be tested because one is anyway using annotations to identify method as test methods. It is also recommended for the reason that it makes unit tests as an alternate form of documentation and avoids code smells. Following is how tests in first example would read like if named using this technique: IsNotAnAdultIfAgeLessThan18 FailToWithdrawMoneyIfAccountIsInvalid StudentIsNotAdmittedIfMandatoryFieldsAreMissing Should_ExpectedBehavior_When_StateUnderTest: This technique is also used by many as it makes it easy to read the tests. Following is how tests in first example would read like if named using this technique: Should_ThrowException_When_AgeLessThan18 Should_FailToWithdrawMoney_ForInvalidAccount Should_FailToAdmit_IfMandatoryFieldsAreMissing When_StateUnderTest_Expect_ExpectedBehavior: Following is how tests in first example would read like if named using this technique: When_AgeLessThan18_Expect_isAdultAsFalse When_InvalidAccount_Expect_WithdrawMoneyToFail When_MandatoryFieldsAreMissing_Expect_StudentAdmissionToFail Given_Preconditions_When_StateUnderTest_Then_ExpectedBehavior: This approach is based on a naming convention developed as part of Behavior-Driven Development (BDD). The idea is to break down the tests into three part such that one could come up with preconditions, state under test and expected behavior to be written in the above format. Following is how tests in first example would read like if named using this technique: Given_UserIsAuthenticated_When_InvalidAccountNumberIsUsedToWithdrawMoney_Then_TransactionsWillFail My personal favorite is naming unit tests based on the writing features of the class under test. It helps me to make sure that a class follows single responsibility. It also aids a great deal in code refactoring. Related: How to Integrate Cucumber for Spring Boot Integration Tests

If you want to modify or add new statuses in Jira, follow this step-by-step guide.

This article will discuss GitHub compliance regulations that CTOs and Security leaders should keep in mind. What is compliance and why is it important?

In this interview, Bob Galen shares his experience coaching an Agile coach struggling to connect with a development manager.

Top six software development engagement models: pros, cons, features, and best use cases. Learn how to choose the best option for your project in this post.

An Enterprise experience with Neo4j graph-oriented DBMS on a JakartaEE RESTful architecture for satisfying frequent changes in software requirements in Agile approaches.

Or is it blasphemy to tweak the "immutable" framework to accommodate our teams’ and organizations’ needs?

What are story points? How does one estimate a story with points? How much time do story points take? Learn the answers to these and more questions.

Discover Agile, Waterfall, and more! Dive into the world of software development methodologies. Learn, compare, and choose the best for your project.

Explore a series of carefully curated collections of essential books, newsletters, podcasts, and tools to elevate your Agile expertise.

Learn more about Java functions and much more.

Agile methodology has become very popular in this digital era. Agile strives to reduce efforts, yet it delivers high-quality features or value in each build.

In this article, we will explore different string reversal algorithms, discuss their approaches, analyze their time and space complexities.

Learn more about ineffective collaboration at the stakeholder level, often resulting in an unsuited reporting system based on misaligned metrics.

Wild West to the Agile Manifesto — Jim Highsmith on the evolution of agile product development at the 52. Hands-on Agile Meetup.

In this post, we'll look at why there are so many definitions of lead time and how you can put them to use.