Bug review - reducing WAD bugs and Sharing with team what the best bugs are like?

As the key output of test teams, we have to monitor our bug quality, reducing WAD bugs, invalid bugs (raised dur to invalid set up, incorrect understanding to requirements, etc). Moreover, bug severity is very important for us and product team, we should monitor bug severity, incorrect severity level will mislead team, eventually have side impacts on project progress.

For example, if one defect didn't lost functionality of one feature, just have some impacts on end users, you shouldn't raise the defect as a major bug. In other hand, if the defect lead to lose the major functionalities of the feature, that should be a major issue, SW team should respond it within 24 hour, and keep the fixing progress once a day.

So if you are a test leader, test manager, a big responsiblity is that you have to coach your team to raise approprate bugs, and that is our topic today. We always drive another series of activities - Best CRs competetition. That is a good thing for test team, through each activity, your team will know what kind of issues you or SW/Product team really care, and what kind of defects really improve our product quality. We provided a little gife - movie tickets or cake coupons to thos guys who won the competetition.

BTW, not all WAD CRs are bad, some of them are very good to product, just SW team follow up requirements or their technique design, so they reject to fix them. By this case, we have to look for help from SW management team or QA team, maybe the defect can't be fixed on this product for schedule reason, but that can be considered on next product if they really bring major benefits to our consumers.

In summary, that is a routine task, you have to put our energy, passion and effors to make them well done.

Good luck, guys.

How do you design your test case? How many steps, and how long is better to execute a test case?

Hi, recently we got feedback on test case quality, some complains on lots of expected results per a test case, that bring a deep discussion on that.
Did you think about the question? What is better for a test case with 5~6 steps and exepected results or just with 1~2 expected results? When you are designing test cases for new features, what should be considered to make sure good quality, easy to maintain, and good coverage, and good productivities to execute them?
I proposed several types of what we meet often, let's check what is the best?
- 5~6 steps Vs 5~6 expected results, each of which should match each step.
Benefits: Can do a completed functionality of a phone, including several interactions, like sending SMS/MMS, or Alarm event, etc;
Weakness: A little complicated, need tester have a full understanding before start to execute, and the coverage is defined from designer's head.

- 3~4 steps Vs 1~2 expected results, just check key points according to requirements, ignoring the common sense points, or minor points to end users.
Benefits: Easy to know the test coverage to requirements, traceable;
Weakness: Didn't deep dive, not enough to check some hidden defects

- 1~2 steps Vs only one exepected result, per my understanding, just check basic functionalities, or sanity test?

Anyway, I personally preferred the 2nd type as main test case model, and sometimes we can use the 3rd type as sanity test in order to quickly go through phone basic functionalities. In most cases, we have to do part regression test after new fixes are built in, or new features are integrated, we can use the 2nd type case with some exploratory test cases.

So what my next question is? How to design an exploratory test case? Any guideline or tips? How to know it meet your expectations? In other words, in black box test, are most of findings from test case executors or from case developers? Why?

Thanks,
Gaochuang

Keep fresh, keep active, then keep opportunities ...

Frankly, it is not easy, but didn’t say no way. In our team, some staffs have 5+ working experiences as testers; they walked through Moto Ezx, LJ platforms, now came to new platform - Google Android. Did you ask yourself, how could I keep fresh after 5 year working in the same team, same jobs? You may not think about it, but that is very important for your career, your life. At least, I often ask myself these questions, basically I can share my several thoughts with you as old friends. Hopefully, they may be useful for you too, but welcome your any comments, you can share your own way on how to do it.

First, don’t lose curiosity for any new cutting-edge technology. Please image how the human being develop the current civilizations, one of the major reasons is curiosity personality for mankind. Man always wonders what he did something that the others never did before, or wonder what the new place is like where nobody in his country went ever, and so on. That is why we found America Continent, we invented train, auto-mobile, car, electronic, etc. So if you still had curiosity for new things in your life, especially for any new changes in your working industry, it should be easy for you to keep fresh, active in your job, even you will be the person who created new records or history, that would be awesome. Anyway, don’t reject changes, which may bring more opportunities in your life, be open-mind to accept the new things, and try to know what happened on that if you really have no idea about that. Of course, here I am saying business things, not our colleague privacy, or some rumors, etc.

Second, take actions!!!
Anyone could approach it if he had taken actions to pursue challenges, goals, and move forward everyday. Nobody can succeed if you always are thinking what it is, but do nothing, except you are Socrates, a great Greek philosopher. That is very important. Basically, most guys are passive to take time do something new, different; especially they have a little idea about them. They may have lots of questions on those new things, but just wait for others to taste them first, that is low risk for them and effective, but they will lose activeness for most things gradually. However, if you really take time to do something different what you didn’t do ever, that will help you have a good feeling, self-satisfied. If you like to taste new dishes by going through Wangjing district, why not taste new technology or new business.

Third, have a good time in weekend.
I don’t know what you do in your last weekend. May I ask you several questions first? Did you feel great last weekend? How often? Did you feel the time consumed very fast last weekend? Did you have a good plan for next weekend and look forward to seeing your friends without one minute delay? If all answers are yes, please skip the following paragraph, if not, I suggest that you should consider my questions again. Actually that is your privilege on how to take it, I didn’t offend it, but that really help you keep refreshed or relax yourself after a wonderful weekend. Please image you are in another world during the 2 days, totally different to what you did in your past 5 days, you may forgot everything you did last week and what you have to do next week, that is very great. I am surely you are different when you came back from another world, with full energy, and like to do anything with very co-operative attitudes. On the other hand, if you feel depressed on Monday, how could you have active attitudes to your incoming tasks? Especially as a tester, you have to test some cases hundreds of times, if you feel disconnected with what you did last week after the great weekend, which may help you feel good. Basically that is a good way to get balance between life and job.

Finally, a good team will help you keep fresh, so everybody have responsibility to create more funs in your work, make your colleagues feel fresh. Actually that need your innovations, how could you make your work funny or get funs from your work? I am looking forward to co-work with those guys who can do that, I think you are them, why not?

In summary, keep fresh, and keep your passions to your work, then keep opportunities …