Jira is a popular tool for software development. One of the ways in which Jira is used for is bug reporting. I’ve recently faced a situation where there was no structure to bug reports in Jira, leaving it completely up to a Tester. I’ll try to argue for why this is not the best practice and how it could be improved.

I feel this topic is really important for many reasons. I also have recent experience that proves people are not that good at this, or they don’t try hard enough. I’ll try to write a bit about this and hopefully convince a few about the importance of good questions.

It’s not a big surpise that different browsers implement different things and behave differently. I’ve, however, focused on one particular area - HTTP cache request headers and how some of the main browsers of today respond to three different user actions.

Like it or not, a lot of time as a tester will be spent checking inputs and whether the system fails or not. One way we can do this is basically using the final product, that is via a GUI interface as a user. We can call a user testing or differently, it’s not that important to remember the eve-growing list of names in software testing, it’s important to use your own brain and think about the testing you do.

A quick recommendation on what to read in the field of software testing.

In language acquisition, there’s the idea of the most common words in a language. It can be interesting to know this when learning a new language. I’ll try to analyze Harry Potter and the Philosopher’s Stone in order to show word frequency and how many of the 1000 most common English words are represented in the book, so one has an idea how much of the book is possible to read when knowing only this set of words (of course it’s a simplification, but an interesting one).

Just a quick article on how to find out BIOS version and how to get an update, and finally how to upgrade it.