Remove Exercises Remove Software Engineering Remove Systems Review Remove TDD
article thumbnail

Effective Software Testing – A Developer’s Guide

Henrik Warne

The author is an Assistant Professor in Software Engineering at the Delft University of Technology. The book apparently grew out of lecture notes from a course on software testing. Instead, it is a tool to highlight which parts of the code have not been exercised, in order to analyze why that is. Test doubles and mocks.

article thumbnail

Here’s Why You Should Write Unit Tests

Modus Create

Software engineers have been testing ever since they could write code. However, the ability to automate software tests commercially emerged only in the 1980s with the introduction of AutoTester. Unit testing is a type of software testing where individual units or software components are tested. Conclusion.

Testing 52
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

How to build confidence as an engineer: an interview with Glen Mailer, CircleCI Staff Software Engineer

CircleCI

From the technical executives to folks on the ground in engineering, management and site reliability, we wanted to know what “confidence” meant to them, and how it had changed over the course of their careers. In this interview, we spoke to CircleCI Staff Software Engineer, Glen Mailer. We hope you enjoy it. And if so, how?

article thumbnail

What I Learned From the First “Testing Without Mocks” Course

James Shore

Qualitative Feedback Seven people (70%) commented that we should keep the exercise-focused format of the course. Software Engineer II I recommend this workshop because it taught me how to effectively test infrastructure without resorting to tedious, slow, and flaky integration tests or test doubles. Exercise expectations.

Course 59
article thumbnail

15 Books by leading software architects

Apiumhub

They range from a general understanding of structure and quality attributes through technical issues like middleware components and service-oriented architectures to recent technologies like model-driven architecture, software product lines, aspect-oriented design, and the Semantic Web, which will presumably influence future software systems.