Ebook: "Getting Started with Test Automation"

Software Testing Proves The Existing Of Bugs

This is not the first time I'm talking about testing for our readers' pleasure. I assume most of you understand the reasons for having tests, QA team members, and dev automation processes. But let me ride a horse that everybody is riding now. Coronavirus. I'll try not to puff your brains out. I promise (writing it in my kitchen at night, here is an egg near me, so...).

The apparent reason for automatization is to remove people from the processes. Or reduce their impact of imperfect choices.

And now it might be late for a lot of businesses (sadly). But it is also an excellent motivator to start using automation sooner rather than later, as you really don't have a choice nor the privilege not to do it anymore.

People are not robots, and sometimes it's terrible for your business. Are you too lazy? Tend to forget what your boss tells you? Made a mistake a while ago? We all have been there. Damn, there are so many cautionary memes around, and we are still making the same mistakes again and again.

Why do airplanes or trains have good safety testing, and your project doesn't? Maybe you are just doing a lousy job, huh? And soon, your project might be replaced or being overgrown by some competitors that decide to act more intelligently.

This newsletter's sponsor - Testim.io, have released a new Ebook: "Getting Started with Test Automation". This book gives a comprehensive introduction to the software testing process.
You can download it here.

If there’s something nagging you and there is always another bug, waiting for you, then it's time to go back to basics. Lockdown is good for reading books. My team lead has a saying about it: "Arthur, costs of hosting are much cheaper than what developers charge per hour". He kicked my ass because of my bad SQL requests. And AWS was a very young and promising service. Now rates are even lower for code storage.

Same with automatization. I'm not rushing you. But if you are leading a team, then you must be smart and responsible, right? Just do some math, some "due diligence".

Often simple but smart things like being cautious, applying TDD, not a "don't-worry-about-it" methodology will pay you some crispy dollar bills. Now, your budget should be smaller, you must be more aware of what is going on. And if I’m correct and your business is related to some custom software, you are the hostage of it.

And money never sleeps.

So do your automated tests, pipelines, and workflow, your logs don't feel sleepy, don't need coffee, and don't have kids they need to feed. Yes, I'm talking bad things, but it's better to hate Bezos than me :) There is a reason why we have replaced horses with metal boxes. You don't need carrots or clean up after your horse (even though we still suck and are using ICE cars).

And, in these times, people will lose their minds, but good and solid process will thrive.

So, why are you wasting your money?

And hey, if you don't know - we now have custom memes on Giphy!

Test-Driven Development is Fundamentally Wrong

By @Cheopys

The second problem here is that TDD presumes that developers should write their own tests. This is supremely ridiculous. I’ve seen this many, many times; the project appears solid to me, I can't break it, but someone else can break it in less than a minute. Why?

Because the same blind spots that I had in design will appear in my tests.

By @oleksii_kh

The problem of ignored bugs is very diverse and bears extremely negative consequences. We all know how traditional testing works at this moment. If you do not devote enough attention to data management, then, as a result, you will receive a whole bunch of ignored bugs. But that’s not all, because as a result, you get an unsatisfied customer and spoil the brand’s reputation.

Obviously services should be designed to be as cohesive and loosely coupled as possible, which means that the can be developed in isolation. However, when this is not practical, or an engineer wants to drive a more production-like test, techniques like service virtualisation and consumer-driven contracts can be useful patterns.

By @David

“Drive” is one of our core values as a company, and I think that comes across in the pace. We’ve been working on the product for about 10 months now, it’s being used extensively by many companies, and we’re getting great feedback on the alpha.

By @mabl

Watch Dan Belcher and Joe Lust present the 4 principles of the Intelligent Testing, and how GCP has allowed us to traverse this era through the development of mabl.

Read More

3 Things Your Manager Should Know About You As Tester

By @mihaelatetcu

Finding defects and spend the time in discussing and documenting them. And then wait for those defects to be fixed, for you to be able to make confirmation testing and then regression testing to be sure that the fixes did not break something else.

By @roesslerj

In fact, one could say that regression testing is the missing link between controlling changes of the static properties of the software (configuration and code) and controlling changes of the dynamic properties of the software (the look and behaviour).

By @michaeltomara

By @vlad.treshcheyko

In a food delivery app example, the Point represents the pick-up location of the order, the drop-off location for the customer, and the delivery person’s location, typically with only their latitude and longitude coordinates.

By @LouisS

Remote scanning is generally limited to remote attacks and other forms of remote detection like our Security Audit Tool. Other remote scanners can attempt to detect the software then run a set of benign attacks from public exploit databases.

By @nkn.org

When a file is being sent, it is first cut into many small chunks (each chunk is 1024 bytes by default) and each chunk is labeled by a sequence number. Then sender sends chunks concurrently using different path and waits for ACK of each chunk from receiver.

By @karan.02031993

A modern fancy word for a smart and efficient coder. (According to me, 10x Engineer is a hype) . Trust me !! You don't want to put that tag in your cv. Only god knows the exact definition of a 10x engineer.

Read More

End to End API Testing with Docker

By @jpfire

No need for any fancy framework. We'll build a generic mock in vanilla JS in ~20 lines of code. This will give us the opportunity to control what the API will return to our component. It allows to test error scenarios.

Read More

Ebook: "Getting Started with Test Automation"

(Download here)

I leave you with this:
"The bitterness of poor quality remains long after the sweetness of meeting the schedule has been forgotten"
- Anonymous

Have a great week,
A rthur from Hacker Noon 👨‍💻

Copyright © 2019 Hacker Noon. All rights reserved.
You are receiving this email because you opted in at our website hackernoon.com.

Our mailing address is:
PO Box 2206, Edwards CO, 81632, U.S.A.

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.