We’ve written about the importance of testing before. If you’re in development, you’re no doubt familiar with agile methodology. But sometimes a test-driven approach seems at odds with going fast. And how do you best communicate the importance of testing to everyone on your team? If you’ve felt frustrated with test-driven development or don’t have buy-in from your team, behavior-driven development is there to help.
The Software Development Life Cycle (SDLC) refers to a methodology with clearly defined processes for creating high-quality software. in detail, the SDLC methodology focuses on the following phases of software development: This article will explain how SDLC works, dive deeper in each of the phases, and provide you with examples to get a better understanding of each phase.
Certifications are a great way to show industry knowledge of specific tools but also display your commitment and passion for the subject. Many big tech players such as Google, Amazon Web Services (AWS), and Microsoft offer certifications to educate users on how to use their tools and services correctly. Besides sharing valuable knowledge, DevOps certification is a great way to onboard new developers and businesses to their platform. But why should you participate in exams to receive certifications?
SOLID is one of the most popular sets of design principles in object-oriented software development. All of them are broadly used and worth knowing. But in this first post of my series about the SOLID principles, I will focus on the first one: the Single Responsibility Principle.
When developing software applications, we want to make sure the application does what the software requirements say it’s supposed to do, and testing proves that it does. In this article, I’ll explore how to link requirements to test cases, and I’ll explain what a requirement traceability matrix is and how to build a simple one.
Being a UI developer, I’ve learned one thing: It doesn’t matter how carefully you write your code. Suppose you’ve double-checked that you defined and called all functions the right way or followed all the best practices. Even then you’ll see that a tiny variable can sneak behind and create an error. Now, suppose you find out that for some unknown reason a form validation or submit button isn’t working.
When I’m writing new software, one of the most important thoughts in my mind is how I’ll test to make sure it works. There are lots of ways to test software, and when you’re at your best, you should be using all of them. Sure, you should make sure that your QA team is able to verify that your code works before it goes live. You should make sure that the code passes acceptance tests, too.
Finding slow JavaScript code can be a tricky problem to solve. Small code changes can have a big impact on the performance of your code. Fortunately, many different approaches can help you nail down the exact source of the problem. In this post, you’ll learn about three methods that’ll bring you the results you’re seeking. You can trust manual code inspection, but that has its disadvantages.
Rostyslav Kosmirak is a .NET developer from Ivano-Frankivsk, Ukraine using Rider and Visual Studio IDE. Kosmirak was not looking for a Dynamic Code Profiler when he came across Prefix. Kosmirak explains that initially he was searching through Google for a log management system when he stumbled on Prefix. Upon downloading, Kosmirak discovered hidden performance problems in his code before they manifested to actual performance problems.
Why is monitoring microservices so important? It’s because we work in a time where systems are complex, distributed across multiple microservices. For example, even a simple e-commerce app may have Ordering, Product Catalog, and Shipping services. Our tooling and practices sometimes struggle to keep up with such complexity.
