I’ve been a regular user of both Windows and Linux platforms. Only after a little while, I started to appreciate the ease with which I can upgrade software and/or the system itself in Linux. In this article, I’d like to have a look at this very thing from the users’s perspective.

Testing can be difficult because of the fact that a Tester might not have enought information to see whether or not there’s a bug. In addition to that, some Testers don’t even look for anything beyond what the see on the screen when interacting with the software. I don’t think this is the best way to gather enough information and uncover enough bugs. Let’s see some other ways how Testers can find information.

Back in 2014, a new issue regarding tabular views was opened on postman’s github page. The issue was closed in September 2019 with a note that Postman started supporting such tabular views. This new feature was released with version 7.7 (only version 7.7.2 could be found in release notes). Let’s have a look what this means and how to work with it in Postman.

Data driven style of writing tests is popular in many different testing tools and/or frameworks. You can use @pytest.mark.parametrize in pytest, you can use templates in Robot Framework and I guess there’re many other examples I don’t have experience with. However, I want to try to use such a style in Cypress. Not that this particular style would be any better than something else, but some people might like the readability of it.

I’ve recently written a small Python script for getting information out of Jira. My motivation was mainly this: going into a browser, refreshing the page or even going to my dashboard can easily take up to 20 seconds (Jira is extremely slow). So I created a small console Python app that gets me all the information I need on a daily basis when testing. However, in the process of doing this, I’ve found out a small but interesting difference between Jira Query Language and SQL.

From time to time, I’m facing the following problem: I need to generate a random (is it really random?) string of a certain length. This scenario can happen mainly from two reasons: 1) I want to generate a new password, 2) I want to test some text field, placing in it an extremely long string and submitting the form (developers must love me). The first scenario could be resolved by many tools, e.g. by Firefox (since version 69) password generator or by some other plugin you install into your browser. However, I still like a bit more not to clutter my computer and software with additional plugins and what not, so why not to build a small tool using stuff already present in my operating system?

It’s really popular to use external tools such as balenaEtcher to flash OS images. Although it’s a good tool, you can accomplish the same task with tools that are already present in Linux systems. Let’s have a look what I mean.