Visibility

Visibility

You can improve your visibility on two areas: the areas that you own, the areas that does not you own.

For the areas that you own, you need dig deeply on this to get the point that you need to work on. More important, you need improve your work method to get better result.

Examples:

1. Code Coverage. You are the owner of team code coverage, you know the information with more details. How do you drive the code coverage. You need clarify several questions:

a. Who will take the action? Feature test owner;

b. Who will drive the action? You, right;

c. Who will check the status and send report;

d. Who will summarize the result after it is done;

e. How about the planning of thing, what are the checkpoint? What`s the goal? When you need send the report? Typically, once for before the checkpoint, and once for the checkpoint;

So, drive one thing is not so easy, besides persuading others to take actions, you also need do Planning, manage the process, report status to stakeholders.

2. Dependency on WB code. Playback has a dependency on Anil`s code. If Anil`s code has any code change, Playback may has break. So Do you think this is a problem? Do you think some solution to resolve it ? If you cannot figure out some good method, Do you have talk with test lead, dev lead, or test manager? Today, I talk with dev lead, and he give me a good solution : give the cases to WB test owner, and run them for each check-in. That`s pretty easy. Right? So first, you should identify that this is an issue which need be resolved, even you have no any clue about this. Then you can think about it and try to get the solution. If you still cannot get any idea, you still have another solution, find help from others. Right?

3. Automation, input data, action(interaction) and verification are independent, So you can write some code ,and when new recording is coming, you even dot write any new code then you can verify this recording.

4. When write test case, you should make clear the dimensionality combination, and all test cases should follow this guideline;

Today, I talked with test manager. Topic is How to improve visibility.

You can impress others in everything, even very small things. You need consider how you can impress others in different condition. Rufus give me a good example: When Beta test pass finished, there is one P0 Active bug and one P0 Resolved Bug in Playback feature. How can you improve your visibility

1. For active bug, You can update more repro conditions, impact on our product(new scenarios that will be impacted), Who is working on the fix, whether more new cases are needed, private check-in process, private test plan.

2. For resolved bug, You can estimate how many codes has been impacted, whether related test cases have been run, Why you will close this bug(what test cases have been run, new test cases have been added, what branch, which build has been verified).etc…..

So event many things have been done by other people, You still have lots of opportunities to improve your visibility.