Mozilla
nhirata
I guess most people don’t know what I’m talking about. Traditional methods are good against regression bugs. Exploratory is good against new bugs. See Firefox 4 time frame. Now I just have to prove it. Filed under: Uncategorized
Continue reading
nhirata
What is true that I have seen, is that the companies where developers do some of their own testing prior to checkin have the least amount of regressions. There was one developer in particular that I recall, people had a … Continue reading →
Continue reading
nhirata
Disclaimer: I am not telling people how to do things. And I do not think I am “better” than anyone else on the QA Team here at Mozilla nor anywhere else. This is to bring a point of view of … Continue reading →
Continue reading
nhirata
I realize now that I have to prove what I have stated in terms of not just bugs, but critical bugs and showing that I can find them faster… Otherwise, I’m just blowing smoke. I get it. I’ll show the … Continue reading →
Continue reading
nhirata
My thought is that “people who have coded at one point in their lifetime may be better QA people than those that have not ever coded.” Why? When I had mentored some new QA members that have coded before… I … Continue reading →
Continue reading
nhirata
So Exploratory Testing gets a bad wrap… mainly because including in exploratory testing is “Monkey Testing” as some call it… which is just banging on stuff. People ask me “How do you find so many bugs?” This is exactly how … Continue reading →
Continue reading
nhirata
Per version of the product per run, could you graph the output of how many bugs a test case produces? Reason I ask is how can we tell the effectiveness of a test case, and what are the best test … Continue reading →
Continue reading
nhirata
I was talking to kaze (that’s his irc handle) about various things over breakfast during work week and we ended up talking about localization and character encoding. I found out through him (and hopefully this will change sometime in the … Continue reading →
Continue reading
nhirata
Here is an outline of notes I have in regards to exploratory testing for new comers that want to QA the b2g project. I will probably get flack for this but oh what the heck. I’ll share my general guideline … Continue reading →
Continue reading
nhirata
What I learned is that there might be 2 different pref locations, the mozilla/*.default folder will contain the global b2g pref if I recall correctly. Here’s some specific steps to pull the prefs.js file: Step 1: PREFS_JS=$(adb shell echo -n … Continue reading →
Continue reading