[Test Engineering Weekly] Test Automation Portfolio, testing serverless apps, bugs in NASA software, the internals of databases

[Test Engineering Weekly] Test Automation Portfolio, testing serverless apps, bugs in NASA software, the internals of databases

Articles

Testing

DevOps. Excellent and easy-to-read articles by Seva Polyakov on how should and should not test Terraform. In Ukrainian!

Testers. Good articles, like good wine, only get better (and more relevant) with time. For example, Michael Bolton says testers should stop doing quality assurance.

Automation. Are you still thinking about how to stand out on the job market? What kind of portfolio can be made for a test automation engineer? Angie Jones answers this question in her post.

Modern. What approaches are there for testing serverless applications?

Useful. Good career advice from Nicola Lindgren. And also - what to do when there is no motivation.

Technical

Rocket Science. The code for space vehicles is written by highly skilled developers. Isn't it? Then how did NASA lose a spacecraft due to a lack of integration tests?

Security. I really like it when complicated things are told in simple words. Or even better - through analogies. In these articles (part 1 and part 2), you will learn about the basic terminology in information security.

Hardcore. I have an article for those who want to learn a little more about some things from the inner world of databases (using SQLite as an example). It is also clearly visible here where those algorithms (binary search) and data structures (B-Tree) are used.

More Hardcore! There aren't many articles on self-testing on the Software Engineering Institute website. But of those that are there - almost everyone - is worth reading. For example, you can read what bugs exist in concurrent systems (and how to catch them). Or - what should be tested on the developer's side (after all, in an ideal world without deadlines).

Distributed systems. A large and practical story about eventual consistency using DynamoDB as an example.

Networks. If you are a real Linux geek, here is a post about the features of TCP buffers. This is really a separate low-level world.

People. Or, more precisely - a story about why people cannot be divided into technical and non-technical ones.

Videos

What am I reading now?

There are so many books I want to read. I find part of it myself, and part of it is recommended to me to read. There are so many books that I'm even thinking of starting a tracker - and reading books according to current priorities. Because time is not infinite!

Now I am reading "Software Testing - A Craftsman's Approach." I have not finished reading the book yet, but even now, I can say that it is interesting. And what is most important - its content is technical and challenging.

For example, the theory of sets and graphs. And yes, these topics can be used in a test engineer's work.

To view or add a comment, sign in

Insights from the community

Others also viewed

Explore topics