Started this discussion. Last reply by Vanita Feb 5, 2010. 18 Replies 1 Like
Started this discussion. Last reply by Ainars Galvans Jul 13, 2009. 7 Replies 0 Likes
Richard Hill commented on Ainars Galvans's blog post Quality is not dead, it’s assessed finally (in few industries)
Richard Hill liked Ainars Galvans's blog post Software testing in banking industry: an uncommon story?Posted on April 18, 2012 at 15:00 0 Comments 1 Like
A few days ago I discovered a bug, developer fixed it and I retested it. The only issue here is – I do not have a “test case” that covers this bug. So how I found it?
I’m testing web service and all my tests are automated, each have it’s setup (crate data), testing (do actions with data) and clean-up (delete data)…
ContinuePosted on March 19, 2012 at 16:58 3 Comments 1 Like
This comes from Wikipedia:
Regression testing is to determine whether a change in one part of the software affects other parts of the software
This is not wrong, but it’s incomplete. Discovering that “a change in one part of the software affects other parts of the software”…
ContinuePosted on February 10, 2012 at 14:30 1 Comment 0 Likes
I have and follow my code of ethics in software testing, do you? My code is simple – I ever do only things that would let me be proud of what I’ve done. Perhaps everyone does so. So I decided to go into a little bit more details here because for me the ethics means that I am ready to (and I did a few times) say NO to my boss or my customer if I don’t believe I could be proud about the results.
So reasons why I refuse to my boss, or my customer doing some tasks or even participating…
ContinuePosted on February 7, 2012 at 8:06 2 Comments 2 Likes
I’m confused when I see people from other industries taking banking industry as example of high quality software caused by high stake/risk. Banking software is far from perfect. Perfect software cost a lot and is illusion anyway. If internet banking sites are more or less user friendly, then back-office and teller software is not much better than green screens form 80ties. There are a lot of back office people doing workarounds, manual fixes, etc. Why so? I think the reason is high…
ContinuePosted on January 17, 2012 at 8:00 2 Comments 2 Likes
I’ve never been recommending doing too detailed test design (scripted tests) before test execution. The only exception was the tests we do to address regression risks. For years I believed that the outcome of a new feature testing must be well chosen tests, documented to the level to make it as fast as possible to do the regression testing. I hated to do the brainless and boring regression tests, but I did them because I knew I should – this is the best practice to…
ContinueJoin Software Testing Club - An Online Software Testing Community
Robert Healy said… © 2012 Created by Rosie Sherry.
