3,104 reputation
21739
bio website none
location Calgary, AB, Canada
age 27
visits member for 2 years, 11 months
seen 5 hours ago

profile for corsiKa on Stack Exchange, a network of free, community-driven Q&A sites

Moderator on sqa.stackexchange - we welcome your QA questions!

Are you a part-time or freelance graphic designer looking for a lightweight project? I'm looking for some sprites :) hit me up at racket.game@gmail.com

Formally known as "glowcoder".

Seasonally known as "corsiKlause Ho Ho Ho".


Jun
23
comment 1.5 Million lines of code. 0 tests. Where should we start?
I noticed this book on a colleague's shelf (on another team.) I take it this book deals with more than just testing?
Jun
23
awarded  Vox Populi
Jun
22
reviewed Approve suggested edit on test-management tag wiki excerpt
Jun
22
reviewed Approve suggested edit on team-management tag wiki excerpt
Jun
22
revised regression-testing wiki excerpt
added 5 characters in body
Jun
22
reviewed Approve suggested edit on test-management tag wiki excerpt
Jun
21
comment Can exploratory testing replace executing manual functional tests?
Having well established standards of behavior are great to aid in guided exploratory testing. Some of our users have been using the same system for 17 years now, and they don't appreciate it when someone makes a new screen that's different from all the rest. One could argue that this is not a bug, but simply a violation of the element of least surprise, but regardless of what it's classified as, it's something that if not caught during testing will get reported as a bug. (Even if it gets shot down, it's going to waste some analysts and manager's time.)
Jun
21
comment What is the difference between regression testing and re-testing?
I think this is a prime example of how the definitions in place in one area/workplace are different from another area/workplace. Neither is wrong, but some will call it different things. That makes it especially difficult during an interview, because you're essentially guessing at what THEY call things.
Jun
21
comment What is shakeout testing?
My understanding is that a "smoke test" was the first step of a "shakedown cruise" - you ran your engines (not in gear) in the harbor, and the smoke rose from the smoke stacks. If it didn't explode after a while, you knew you could try actually putting the engines in gear. Chances are you would have to make some calibrations after the smoke test before putting it in gear though. Note the historical accuracy and etymology typically have little bearing on day to day usage, so they very well may have merged. :)
Jun
21
comment What criteria do I apply to a highly complex development project to warrant getting “real world” data?
Well, it's twofold. If the data exists, and it illustrates a problem, you know you have a problem and that has to be handled. But on the other side of things, you also have to consider that if you can't reproduce the problem you don't have a good chance of really fixing it. All too often, this translates to "well just write some code to fix it when it's messed up" which means they don't find the real cause of the problem, so they don't really know what else is getting corrupted.
Jun
20
comment What is shakeout testing?
Wouldn't worry about it? How can you interview a position without an extensive supply of buzzwords?!
Jun
20
answered What is shakeout testing?
Jun
17
comment Writing tests to learn the code
With a little luck, a jumping off point will show up in their "training" (which is the first time we've ever had formalized training for developers, it's too bad they didn't have it 8 months ago when I joined the team. :-) )
Jun
17
comment What are guidelines to use for exit criteria when releasing?
Are we missing an F the title? :-)
Jun
17
answered What criteria do I apply to a highly complex development project to warrant getting “real world” data?
Jun
17
comment What criteria do I apply to a highly complex development project to warrant getting “real world” data?
I can't tell you how many times I've gotten a spec from someone, looked in the code and found their feature already existed, they just had to turn it on...
Jun
17
comment Writing tests to learn the code
<puts on user hat> Our SME's are highly unlikely to spend time with a developer who isn't directly working on one of their projects. And they might be experts in manufacturing, but they know only enough to get by about the system. A lot has been lost to tribal knowledge when people left. Same with req's and specs. We do have user manuals and sample screens they can use, as well as development systems where they can't screw up any data (we just refresh the database every so often anyway.) That would allow them to explore (which is important for learning) while writing tests.
Jun
17
comment Writing tests to learn the code
<puts on mod hat> Sorry, there's no way to un-CW a post. I noticed that when you posted the question, but apparently there isn't a way. :-( Which is too bad, this is a good answer and I think you deserve the rep for it.
Jun
17
comment Writing tests to learn the code
I suppose their work does have to be reviewed. I don't know if they're skilled employees or not. When I graduated uni, I already had over 5000 hours writing production code (most of my peers said their internships were getting senior devs coffee and web-surfing. At the time I thought they were lucky; turns out I was the lucky one!) I don't know what kind of previous experience these guys have, their GPA, or anything. I'm just a dev here. But, I take my manager's words seriously when he says "try to find ways to improve the team." If he didn't actually mean it, he shouldn't've said it! :-)
Jun
17
revised testing Touchscreen driver
cleanup