There is a colorful and lively rainforest being uncaringly grown daily on most of the servers out there in the never sleeping on-line world.
Round-the-clock running servers write out a lot of potentially interesting data and each day produce a humongous harvest of logs.
As a developer, have you ever thought about the person who will actually be reading your log lines? Here’s a look on the logging from that man’s perspective.
JMeter was originally created as a load and performance test tool, but thanks to its constant development it offers other possibilities, one of which is automating a simple (but useful) regression test. Because of its very handy features like the assertions, extractors and listeners, automating a regression test in JMeter is fairly easy to set up, run and view the results.
In the old days we could qualify bugs in different scales – severity, impact, visibility, class and priority. This practice seems to be abandoned in favor of easier project management so there is frequently only one field. However, making only one field available for depicting bug importance hasn’t helped much in qualifying bugs critical or making decision on how soon is the fix needed.
There are lot of disputes about scripted vs. exploratory testing. Here is a modest attempt to…