I’ve recently writen 200+ API tests in pytest across two different APIs, so I feel like summarising (mostly for my future self) some key points. Perhaps it might be useful to others as well, so I’ll write it as a blog post.

Following up from the previous article, I’ll leave one quick setup here that I currently use to set up base url for different environments.

Git offers aliases for its commands, which is a nice way to make some commands shorter or more memorable. Let’s see how to create and delete such git aliases.

There has been more JS based testing frameworks recently, Cypress is perhaps the most popular out of them, but today, it’s time for TestCafe. I’ve decided to write a complete set of e2e tests for a small system in TestCafe. I made the decision on Tuesday when I only knew there’s such a thing as TestCafe, but never worked with it before. I finished on Thursday (technically on Friday at about 1 a.m. at night :D), that’s about 2 days from zero to 48 e2e tests across multiple pages in the app. 25 commits in total. Let’s sum up what I experienced and perhaps compare TestCafe with Cypress and others a bit.

One of the features git supports is tags (see $ man git-tag), which is another useful bit that can help you find more information quickly. Let’s have a look at some basics, and what I use these tags for.

It’s always fun to know how things we use daily work on a lower level. DHCP is one of these things many of us use on a daily basis and yet we probably don’t know so much about it or at least don’t really think about it. I’ll summarise some bits and pieces about this protocol and how DHCP opertion usually works, plus I’ll set it up using a Cisco IOS on a Cisco 1841 router.

Git offers so many commands and options that it’s virtually impossible to remember them all, especially when one doesn’t work with them daily. However, git also offers automatic completion that it perhaps not very knows but nevertheless very useful.