Negative testing is something I've done as long as I've been in QA, but isn't a term I was familiar with - so I never actually classified the negative testing I was doing as anything other than testing. I heard the term used for the first time at my most current job; a recent interviewee was asked to negatively test a water bottle, which had us all stumped for a bit. Negative testing is how you test your application for …
Category: QA
I won't lie, positive testing, to me, tends to be one of the most boring, albeit incredibly necessary, types of testing. It is seriously so important, but for some reason is the one of the only ways of testing I find super tedious; I think it's because I'm naturally pretty creative so having to do a certain set of steps only, to test if something works correctly, tends to be pretty boring. I actually rarely ever just do one type …
So, you know how when you leave a camp site you put out the fire, then do a double check as you walk away, and sometimes go back and put your hand over it again, just to make sure? Well, that's pretty much what smoke testing is. Checking to see if, at the end, something has gone wrong, or is "smoking". At work sometimes we have data issues in our test environments. When you don't have accurate data it's hard …
The other day I was super busy at work; in meetings about a new product, while also working on a release. I was getting a lot of pressure to get the release out ASAP, and trying to test while also participating and taking notes in my meeting - yeah...not a fantastic idea. We had to pull others in to help test, other people that aren't QA Engineers, and you know what testing was skipped? Integration testing. The release got pushed …
I love day planners, making lists, rearranging things, even packing and unpacking to move, because I love going through things and organizing. So, test plans are totally my jam. They are an excuse/reason to channel all of my annoying organization quirks into something actually useful to more than just myself. I usually try to have a planning meeting with devs, PM, and QA to talk through where we are, what I think needs to be tested and how. I also …