Heuristics
June Issue of AST Update Now Available
Submitted by sbarber on Fri, 22/08/2008 - 18:48. general software testing | heuristics | industry recognition | metaphors | other online resources | perspectives
June 2008 Issue of the Association for Software Testing Magazine and Newsletter Now Available
Latest Column -- Inspired by taking AST's Bug Advocacy Class
Submitted by sbarber on Fri, 04/07/2008 - 05:54. bug tracking/incident management | context-driven testing | functional testing | heuristics | other online resources | perspectives | project management | test managementSoftware testing is improved by good bug reporting
I recently completed (successfully, I might add) the second of the Association for Software Testing's all online, free to members Black Box Software Testing course. Each of these courses is four weeks in length. I've been involved with this program since years before it became a program, and I am an instructor for the first course in the series, called Foundations. For this course, called Bug Advocacy, I was a student.
Grey-box techniques for excluding tests
Submitted by Ainars Galvans on Mon, 30/06/2008 - 13:33. heuristics Don’t test the reused code tested previously – you will have more time to test new code. This heuristic for a black-box tester is basically all the idea of this blog – one I was creating for a week … I started this as blog about techniques, but wanted to be clear about grey box. A research on the term ended quite a long story below. If you don’t care about it – scroll down to the last chapter describing the techniques.
Linguistic heuristics
Submitted by Karen N. Johnson on Sun, 22/06/2008 - 06:05. databases & SQL | heuristicsSearching. I’m currently testing a product that has a search feature. I’ve tested search functionality before but not a multilingual search engine that utilizes two different search engines based on the language selected. Nor have I previously worked with a search engine that uses stemming and stop words.
I almost didn’t want to write about this – figured I would wait until I resolved my challenges before writing about it – but it occurred to me why? It’s not as though in software testing I haven’t learned that first understanding the complexities of a problem is an essential starting point.
I almost didn’t want to write about this – figured I would wait until I resolved my challenges before writing about it – but it occurred to me why? It’s not as though in software testing I haven’t learned that first understanding the complexities of a problem is an essential starting point.
Testing Lessons From Civil Engineering
Submitted by sbarber on Sat, 21/06/2008 - 07:13. context-driven testing | development methodology | events | functional testing | general software testing | heuristics | patterns | perspectives | test analysisBelow is the paper I submitted as a prologue to an experience report, discussion, and (hopefully) additional research that I'm presenting for the first time during:
Reliability is not only about overload: RANDOMize your system state
Submitted by Ainars Galvans on Thu, 24/04/2008 - 17:15. heuristics | reliability testingI never used mnemonics. Never say never... Here is my own mnemonic. Double RANDOM stands for ReadRights AalternativeAccess, NoNetwork, DesynchronyzedData, OutOf(whatever resource), MinMax(installation). Depending on context (e.g. reliability requirements, etc.) I spend more or less time trying to emulate system states unexpected by developer and thus unhandled by code.
ET thoughts: The Seeker (CKA) heuristic
Submitted by Erik Petersen on Sun, 20/04/2008 - 07:53. exploratory testing | heuristicsSome people are more into mnemonics than others. I can recall walking along with James Lyndsay one day. This in itself was unusual because we are normally on opposite sides of the earth. We were discussing how there are many great mnemonics for test ideas, but neither of us was able to recall the items, just the mnemonics! I think this strongly influences our exploratory testing approaches. Alan Richardson has blogged about this here . Because it is general, It doesn’t really need a mnemonic, but I will give it an acronym. Seeker, CKA, Challenge Key Assumptions. While any tester can do this, the experienced tester will be more skilled at identifying key assumptions, and be more effective at using it. If you have less experience, or can remember mnemonics (!), maybe try the standard ones! You’ll find some links by searching for “test ideas” at my testingspot.net site
Training for Performance Testers in Brighton UK, May 08.
Submitted by sbarber on Mon, 07/04/2008 - 04:13. context-driven testing | events | general software testing | heuristics | non-functional testing | performance testing | project managementScott Barber has teamed up with Rosie Sherry of DrivenQA to bring PTSS Training to Brighton & Hove, UK.
Sign-up now for Performance Testing for Managers or Performance Testing for Software Systems; A Heuristic Approach.