New people on the block
A great service starts with great people. So we hired some more.
A few days ago the LaLa Lunchbox app landed on App Store. Even after such a short time, it got some great feedback. Things like that happen if you have a client that knows what problems need to be solved, but is flexible enough to let the professionals do their work. This post is about […]
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.
One of the best things in shells is that you can do some repetitive tasks quickly, efficiently and painlessly. For example, you have to replace some string with another string in multiple files scattered through different directories. You can do that using GUI editors, but this proces is not quick, it is dubiously efficient and […]
Some software testers often write shell scripts to make life a bit easier. But real power of shell lies in shell itself, in so called “oneliners” which UNIX and Linix admins (and also testers in UNIX environments which I used to be) so much love and use. When transfered to Windows environments, those guys will […]
There are lot of disputes about scripted vs. exploratory testing. Here is a modest attempt to make more obvious some of advantages of later tasting approach. 1.Â ET is more agile Even if Agile manifesto is nearing its first decade, â€œAgileâ€ is word which still sounds like a buzzword in IT business. It sounds so […]
Every now and then in my daily work I recall wrong definitions of software testing and it’s purpose which Glenford J. Myers used to prologue the chapter “The Psychology of Testing” in his great book The Art Of Software testing . Here are those bad definitions: â€œTesting is the process of demonstrating that errors are […]
Lately, in software development lifecycle, vastly formalized requirement documents are being replaced by more agile, so called “user stories” which are actually short software requirements formulated in users own words. User stories are created by the customer or it’s representative preferably in the meeting with developer. User stories should be short and have in focus […]