Writing documentation could be a real trouble mostly because one of the two reasons: 1) it takes time, 2) documentation has a tendency not to stay in sync with the actual code. I’ve recently written some JavaScript code and was in need to convert JSDoc comments into Markdown used in README.md. I’ve not found any tool I could use here, so I’ve eventually took some time to write a Perl script to do it for me. Here it is.

It’s crucial for Testers to know different data exchange formats. JSON is one of them. It’s become popular as an exchange format for web services as well as a format for configuration files.

Long time no new article here! It’s been almost two months. However, I’ve been writing a book about e2e tests in TestCafe. You can get it on leanpub now.

A common trouble with e2e automation testing is how to test sending/receving emails. I’ve seen various Gmail accounts Testers create, I’ve seen how Testers want to check a received email on Gmail via its GUI. Neither approach is effective because testing via a GUI is slow and flaky, the other approach is undoable completely since Google blocks automation scripts like Selenium. How should we do it then?

Last Manjaro update was not very smooth for me because I eventually managed to lock myself out with no option to log back in to my sestem. Not that it was caused by the update itself, it was caused (of course) by me not paying enough attention to what was being updated.

Many people have a well-formed expectation when it comes to rounding. We’ve all learnt this during the early years in school, right? But such expectations can become a source of bugs that are hard to find. Let’s have a look.

I’ve recently started playing around with R, which also translates into installing additional R packages. Right at the beginning, I ran into two problems which I’ll explain here now.