Skip to content

Latest commit

 

History

History
168 lines (126 loc) · 14.8 KB

tdd.md

File metadata and controls

168 lines (126 loc) · 14.8 KB

drawing

Debugging in a docker container isn't that straightforward. At least it is not in the way my team set everything up. I will describe my methods for debugging.

Python's simplicity permeates it all, and tests are not an exception. I left behind -temporarily- my JUnit and Mockito days by pytest and unittest.

It isn't about being diligent. It's because we've forgotten what we knew.

Build your products based on the testimonials you want to get from your customers

If you ever used an ORM, you already know that it can save a lot of time, especially when starting a project, but as the codebase grows it can become impossible

It sounds backwards because it really is

How to get rid of the weird styled component names in test snapshots

Selenium is a open-source free and automation testing tool for web applications across all different browsers. It is quite similar as HP QuickTest Pro (QTP, currently UFT). However, Selenium mainly focused on automating web-based applications. So the testing done using Selenium tool is referred as Selenium Testing.

In order to record a test, follow the given steps: Step 1 : Open Mozilla Firefox web browser, go to tools and click on Selenium IDE. There type the link

Intro

Alex is a software engineering veteran with over 30 years of hands-on professional experience. He is a staunch advocate of Extreme Programming and TDD.

In this article we will review some best practices and must-have libraries which will get your unit tests to the next level.

Methodology to enable fast development of robust enterprise applications applying Test-Driven Development (TDD) and Hexagonal Architecture.

Intro

Test Driven Development puts emphasis on unit over integration tests. The result can be lower quality featuring bugs that are baked into the product.

The Conquest and Conquer is an analogy for serious software development. I will combine the TDD solution with an automated code generated using Artificial Intel

Photo by ShareGrid on Unsplash

Your Practical Introduction to Test Driven Development

Tips that would help you build integration tests using RSpec and Capybara.

When we start developing an app we usually do it the old fashion way: we get an idea, we elaborate on it, we make a plan to develop an app then we start coding and in the end, we test if our app is working properly.

No matter if you are a startup company or a big enterprise, your app needs to be intuitive and customer-facing to win many hearts. However, designing a user-friendly web app for your business is not so easy. You need to be aware of the complete rules. 

I Had an Idea

Developing a complete word game is very easy with TDD

Here's why you need to know TDD craft.

I use Jest nearly every day when working, and it's a fantastic tool. It lets me ship my code with confidence, knowing that I have produced something which works as intended.

Excessive concern about the beauty of the source code can compromise the outcome of a project.

Best Practice Cover DotNet (.NET) CSharp (C#) with unit tests with Test Driven Development TDD Dependency Injection DI Inversion of Control IoC Containers

Until I stumbled upon TDD, I had never really understood tests. I remember writing a whole project without tests and publishing it. Can you believe it?

High unit test code coverage is often viewed as a key indicator of code quality, but it's important to focus on the quality of the unit tests, not just the cod

I stumbled upon a thread recently where the question was posed, “What are some common mistakes when refactoring code?”

Test Driven Development (TDD) is a software development cycle that focusses on describing the behaviour of your code first using tests

We keep practicing this amazing Kata and learning. You can follow the steps!

I got into the habit of doing about 30 minutes of Code Kata every morning. I practice these Kata following the test-driven development (TDD) approach.

This is some thoughts about TDD and how things don't always work out perfectly even with the best-written tests when developing new software on a deadline.

Intro

The text you are about to read describes an imaginary dialog between two programmers on their way to discover the orgastic pleasures of a library called asyncFn.

In this story we will try to see how to improve a simple REST connector that places a request on an external service through an HTTP POST call and returns the result back from the remote server. The full example can be found here. Following is the source code for our connector (Connector1):

Test-driven development (TDD) is all the rage these days and has been a discussion topic for quite some time. If you are brand new to TDD, this article should serve as a good introduction to what TDD is, why it’s useful, what a typical TDD workflow looks like, and when to use TDD.

We all love T.D.D. We know its benefits, we have read a thousand tutorials on how to build a system using this technique. But this not feasible for currently legacy systems.

In the recent sweltering world heat wave, I was set a tech test the other day. In it I needed to write a function that would output zero to five depending on its 6 combinations. For this example I’ll say we wanna get the outcome of flipping a coin and playing rock, paper, scissors translated into a number ranging from 0 to 5.

This post contains a step-by-step example of a refactoring session guided by tests. When dealing with untested or legacy code refactoring is dangerous and tests can help us do it the right way, minimizing the amount of bugs we introduce, and possibly completely avoiding them.