Showing posts with label testing strategy. Show all posts
Showing posts with label testing strategy. Show all posts

Tuesday, September 3, 2013

Is that why all the testers asked me to friend them?

The business asked for a social amplification feature.  Now every time you successfully use our app it shares it to the screen of someone who recently got an error message.

I considered claiming I did a Snarky yesterday, a whole day early, and just posted an empty panel with an empty title in honor of Labor Day.  Instead, I truly embraced Labor Day, so I'm about 10 hours late given my usual posting schedule.  After someone actually used this phrase in front of me, I knew it had to be a snarky.  I'm considering using it in all the proof of concept UX/UI designs I write, just to be a smart ass.  Except someone would give me an award for a good design, and then I'd be mad.

The following was an alternative title and snark:
Snarky: I added social amplification.  Every time you use our app, your friends get notified.
Title: Does that means I don’t have friends, or I don’t have friends that use our app?
"Amplification is the concept of taking a positive action – a purchase, a light-touch interaction or full-on review – saving it and then sharing it far and wide. After all, 90% of us trust recommendations from friends – so surely it makes sense to push the genuine endorsements we do receive to their absolute limit?" - http://oursocialtimes.com/4-examples-of-social-media-amplification-in-action/
Snrky: The business asked for a social amplification feature.  Now every time you successfully use our app it shares it to the screen of someone who recently got an error message.
Title: Is that why all the testers asked me to friend them?

Thursday, August 22, 2013

Well have you found any bugs yet?

My new testing strategy is to start randomly deleting lines of code to see what breaks.
It goes against logic, or so it seems, to let a developer spend too much time testing, but I think there might be something to it -- at least once you approach the acceptance testing phase.  There is just too much temptation to veer towards "fixing the code" rather than "fixing the bugs" what with the source code just right there.  What's worse, even if they do focus on "fixing the bugs", one must first find said bugs, which from the developers perspective means being told,  "No we just assume your code is definitely broken (even though you might actually be a little bit proud of it),  so go find all the broken stuff and fix it."  How depressing, not to mention boring.  And you wonder developers hate testing?


Title: Well have you found any bugs yet?
Snarky: My new testing strategy is to start randomly deleting lines of code to see what breaks.