Friday

When to bring up issues with peers

Sometimes after I teach a peer-to-peer feedback workshop, people go back to work and run amok. They give feedback on every little thing and every minor irritation.

That doesn't help...but the rule of three might.

Keep in mind that the over-arching goal of peer-to-peer feedback in the work place is to improve working relationships and work results. That means you don't get to give feedback about issues that don't affect either of those areas--doing so can damage working relationships.

But if you find yourself feeling irritated about small things--for example, the way someone cracks his knuckles or chews gum--it may be a sign that you haven't given feedback about something that does matter, like a pattern of behavior that affects the work.

As an aside, I think the title of the HBR piece, "When to Confront Someone," is unfortunate. Most people don't like confrontations and will go out of their way to avoid them.

When feedback conversations and negotiating working relationships are characterized as confrontations, they seem bigger, scarier and riskier than they need to be.

Paradoxically, avoiding the conversation when issues are small increases the likelihood that things will escalate to a confrontation.

Amplify’d from blogs.hbr.org

I have a rule for dealing with these types of situations — times when I'm not sure if it's worth raising an issue. I need a rule because it's often hard to know if something's a big enough deal to address until it's too late and then, well, it's too late. It's already gotten out of hand. On the other hand if I jump on every single issue the first time it comes up then, well, I'll be out of hand.

The first time someone does something that makes me feel uncomfortable, I notice it. The second time, I acknowledge that the first time was not an isolated event or an accident but a potential pattern and I begin to observe more closely and plan my response. The third time? The third time I always speak to the person about it. I call it my rule of three.



You can read more about these at : http://estherderby.amplify.com/2010/10/07/when-to-bring-up-issues-with-peers/

Testing Cycle

Wednesday

Access violation error in Quality Center

Issue#1 :


Access violation error

When I try to edit some test case in test plan. I'm getting access violation error.

Can someone please help me resolve this issue.

"Access Violation at address 0B2DF128 in module 'QCLIE~1.OCX'. Read of address 000000E0"



Probable Solutions :


1. suspect that the OCX file needs to be registered.

How to Register an OCX file

If you are receiving errors about an ocx file, registering the
file may solve the problem. To register an ocx file simply
follow the simple steps below.


* the file using windows explorer or My Computer.

Alternatively search for the filename.

* down the shift key and right click on the file. Then click

'Open With...' from the menu.

* 'Open With' dialog box should appear. Click the button

'Other...'.

* to your windowssystem32 directory and select the file

'RegSvr32.exe'. Do a file search for it if you have trouble
locating the exact folder. On Windows 2000 it is typically
located in c:WINNTSystem32. Click Open to select the file.
Then click OK on the 'Open With' dialog.

* should see a message indicating the file was successfully

registered. If you see an error message, try restarting your
computer and going through the above process again.

Bonus : visit : stqadiscussions.blogspot.com for all QC errors

Let me know if this resolves your issue


2. Remove TEMP files, browser history , Cookies and close opened other applications and restart the system then try,let me know if this resolves your prob.


3.Do you have versioning enabled on that project? If so, I wonder if maybe the item has a "checked-out " status somewhere? This may not be the case but a couple of things you can do are.

1. Run Verify & Repair (if needed) on the project.
2. Check for checked out status. In the project, set your filter to show all items that are set as "checked-out". This should show you all that are checked out. Be sure to look in the hidden areas of the filter screen as there are a couple of other places the version status field is located.
3. Bounce your server. If it's a Windows box, the ultimate "fix-all" provided by Microsoft usually works. ;-)


4.First off, to answer your questions, No, doing a V&R won't impact existing integration. Well I should say it shouldn't. The only thing I can think of that could possibly be impacted would be any custom code that has been used for the integration. Although I highly doubt it would be impacted but there is always that 1 in a billion chance it could. What I would suggest is to backup (or export) the project before you run the V&R just in case. We have one project that is highly customized and has a lot of code in it and so far it hasn't been affected by the V&R. The V&R mostly corrects any data integrity issues.

Checked out items will only be available if your project has versioning enabled. You can check for this in the Admin side by selecting your project and look at the menu bar above the project in the main body. (I'm sure there is a technical term for that but I can't think of what it is.) and you'll see an option for versioning. (At least in QC 10 and 11, I don't know about 9.) It will tell you if versioning is enabled or not. If not, then you don't need to worry about it.

The Long way:
If versioning is enabled, then log out of the admin and log into QC under your project that does have versioning enabled. (Under Requirements, Test Lab, Test Plan, Test Rescources, and Defects you can do this.) use your filter and look for "Version Status" as one of your selections. Choose the "Checked_Out" option. Now you can use the "=" symbol off to the left if you want but I haven't really noticed any difference in not using it.

On some areas there is a minimized section, this may also contain a version status selection on some of the areas, be sure to select it as well.

Once you click it will display all the checked out items.

Another way to do it is in the administrator section. (a lot easier in my opinion)

Go to your project.
Expand it to see the database columns.
You can click on the VER_CTRL column to get a quick overview of what is checked in or checked out.

There are a couple of other columns you may want to look at as well. These are:
VC_TEST
VC_REQ
TEST
REQ

In columns that have a lot of results, you can create a SQL script to find just the checked out ones.

This will also give you the related items to it like test ID, Father ID and so on. Once you have that, you can then do a search by using the filter for those items and check them in. (the undo Checkout option in the project side.)

If you haven't, I would definitely read through the admin and user guides as they actually do have a lot of good information in them. If you can't find the answers you need there then this group is awesome for getting help as there are a lot of really knowledgeable people here. Also check out the HP and Vivit forums as there is another really good source of info.

Administrating QC isn't really that difficult until you get into custom content. From my experience I find it easier to use the "out of the box" approach. if you can avoid customizing then do. It makes your job a lot easier. QC does have some "archaic" interfaces and could use an upgrade in those areas, you'll discover those as you work in the application.

Some key skills you should probably look into for administrating QC are SQL and VBScript. These are two areas that you'll find a lot of use. I'm not to great at either but am self teaching so I can take advantage of them. Also, if you don't admin the database, get to know your DBAs. Buy them some donuts now and then and they will be your best friends.


5. when it comes to errors like the one you posted or the .OCX issues I've found that if you run the registry part of CCLeaner on the users system then relaunch HPQC in the browser, it will download the components again and everything should be fine. Sometimes the registry entries for those items get corrupted and CCLeaner will clean that up.


CCleaner is a free tool and is just plain awesome. you can find it at www.piriform.com.




Access violation error in Quality Center

Issue#1 :


Access violation error

When I try to edit some test case in test plan. I'm getting access violation error.

Can someone please help me resolve this issue.

"Access Violation at address 0B2DF128 in module 'QCLIE~1.OCX'. Read of address 000000E0"



Probable Solutions :


1. suspect that the OCX file needs to be registered.

How to Register an OCX file

If you are receiving errors about an ocx file, registering the
file may solve the problem. To register an ocx file simply
follow the simple steps below.


* the file using windows explorer or My Computer.

Alternatively search for the filename.

* down the shift key and right click on the file. Then click

'Open With...' from the menu.

* 'Open With' dialog box should appear. Click the button

'Other...'.

* to your windowssystem32 directory and select the file

'RegSvr32.exe'. Do a file search for it if you have trouble
locating the exact folder. On Windows 2000 it is typically
located in c:WINNTSystem32. Click Open to select the file.
Then click OK on the 'Open With' dialog.

* should see a message indicating the file was successfully

registered. If you see an error message, try restarting your
computer and going through the above process again.

Bonus : visit : stqadiscussions.blogspot.com for all QC errors

Let me know if this resolves your issue


2. Remove TEMP files, browser history , Cookies and close opened other applications and restart the system then try,let me know if this resolves your prob.


3.Do you have versioning enabled on that project? If so, I wonder if maybe the item has a "checked-out " status somewhere? This may not be the case but a couple of things you can do are.

1. Run Verify & Repair (if needed) on the project.
2. Check for checked out status. In the project, set your filter to show all items that are set as "checked-out". This should show you all that are checked out. Be sure to look in the hidden areas of the filter screen as there are a couple of other places the version status field is located.
3. Bounce your server. If it's a Windows box, the ultimate "fix-all" provided by Microsoft usually works. ;-)


4.First off, to answer your questions, No, doing a V&R won't impact existing integration. Well I should say it shouldn't. The only thing I can think of that could possibly be impacted would be any custom code that has been used for the integration. Although I highly doubt it would be impacted but there is always that 1 in a billion chance it could. What I would suggest is to backup (or export) the project before you run the V&R just in case. We have one project that is highly customized and has a lot of code in it and so far it hasn't been affected by the V&R. The V&R mostly corrects any data integrity issues.

Checked out items will only be available if your project has versioning enabled. You can check for this in the Admin side by selecting your project and look at the menu bar above the project in the main body. (I'm sure there is a technical term for that but I can't think of what it is.) and you'll see an option for versioning. (At least in QC 10 and 11, I don't know about 9.) It will tell you if versioning is enabled or not. If not, then you don't need to worry about it.

The Long way:
If versioning is enabled, then log out of the admin and log into QC under your project that does have versioning enabled. (Under Requirements, Test Lab, Test Plan, Test Rescources, and Defects you can do this.) use your filter and look for "Version Status" as one of your selections. Choose the "Checked_Out" option. Now you can use the "=" symbol off to the left if you want but I haven't really noticed any difference in not using it.

On some areas there is a minimized section, this may also contain a version status selection on some of the areas, be sure to select it as well.

Once you click it will display all the checked out items.

Another way to do it is in the administrator section. (a lot easier in my opinion)

Go to your project.
Expand it to see the database columns.
You can click on the VER_CTRL column to get a quick overview of what is checked in or checked out.

There are a couple of other columns you may want to look at as well. These are:
VC_TEST
VC_REQ
TEST
REQ

In columns that have a lot of results, you can create a SQL script to find just the checked out ones.

This will also give you the related items to it like test ID, Father ID and so on. Once you have that, you can then do a search by using the filter for those items and check them in. (the undo Checkout option in the project side.)

If you haven't, I would definitely read through the admin and user guides as they actually do have a lot of good information in them. If you can't find the answers you need there then this group is awesome for getting help as there are a lot of really knowledgeable people here. Also check out the HP and Vivit forums as there is another really good source of info.

Administrating QC isn't really that difficult until you get into custom content. From my experience I find it easier to use the "out of the box" approach. if you can avoid customizing then do. It makes your job a lot easier. QC does have some "archaic" interfaces and could use an upgrade in those areas, you'll discover those as you work in the application.

Some key skills you should probably look into for administrating QC are SQL and VBScript. These are two areas that you'll find a lot of use. I'm not to great at either but am self teaching so I can take advantage of them. Also, if you don't admin the database, get to know your DBAs. Buy them some donuts now and then and they will be your best friends.


5. when it comes to errors like the one you posted or the .OCX issues I've found that if you run the registry part of CCLeaner on the users system then relaunch HPQC in the browser, it will download the components again and everything should be fine. Sometimes the registry entries for those items get corrupted and CCLeaner will clean that up.


CCleaner is a free tool and is just plain awesome. you can find it at www.piriform.com.




Monday

OBRM OR ORACLE BRM Table Structure

The Oracle Billing and Revenue Management (BRM) database structure can be confusing at first glance. Rather than following a typical relational design, BRM was designed to support an object-oriented approach for extensibility.

This post describes the logical relationships that exist between tables so you can get started.

First, a table is either a Parent table or a Child table. The Parent tables are usually one word table names with “_t” on the end. For example:

  • Account_t
  • Bill_t
  • Item_t
  • Event_t
  • Service_t
  • Profile_t
  • Payinfo_t

The Child tables’ names always start with their Parent table’s name. For example:

  • Account_nameinfo_t (child of account_t)
  • Account_products_t (child of account_t)
  • Event_billing_products_t (child of event_t)
  • Payinfo_cc_t (child of payinfo_t)

Parent tables are logically joined to their Children tables by the poid_id0 (please note that’s a zero at the end of the poid_id string) column in the parent and the obj_id0 column in the Child table. Here’s a sample select statement:

Parent_table.poid_id0 = child_table.obj_id0

For example, account_t.poid_id0 = account_nameinfo_t.obj_id0

Some Child tables will join back to other Parent tables. For example account_products_t joins to the service_t table by account_products_t.obj_id0 = service_t.account_obj_id0 and account_products_t.service_obj_id0 = service_t.poid_id0. These are bi-directionally joined.

===================================================

That above paragraph addresses parent/child table relationships in BRM. But how do parent tables relate to other parent tables?

Parent tables are joined together by their poid_id0 columns.

Not all parent tables join to each other but when they do it will always be parent_table.poid_id0 = joined_parent_table._obj_id0.

For example, account_t and service_t are joined by account_t.poid_id0 = service_t.account_obj_id0

It is always easy to see the relationship in the tables by looking at the columns. Poid_id0, obj_id0, and anything that ends in obj_id0 (like account_obj_id0, service_obj_id0, etc) are the joined columns.

OBRM OR ORACLE BRM Table Structure

The Oracle Billing and Revenue Management (BRM) database structure can be confusing at first glance. Rather than following a typical relational design, BRM was designed to support an object-oriented approach for extensibility.

This post describes the logical relationships that exist between tables so you can get started.

First, a table is either a Parent table or a Child table. The Parent tables are usually one word table names with “_t” on the end. For example:

  • Account_t
  • Bill_t
  • Item_t
  • Event_t
  • Service_t
  • Profile_t
  • Payinfo_t

The Child tables’ names always start with their Parent table’s name. For example:

  • Account_nameinfo_t (child of account_t)
  • Account_products_t (child of account_t)
  • Event_billing_products_t (child of event_t)
  • Payinfo_cc_t (child of payinfo_t)

Parent tables are logically joined to their Children tables by the poid_id0 (please note that’s a zero at the end of the poid_id string) column in the parent and the obj_id0 column in the Child table. Here’s a sample select statement:

Parent_table.poid_id0 = child_table.obj_id0

For example, account_t.poid_id0 = account_nameinfo_t.obj_id0

Some Child tables will join back to other Parent tables. For example account_products_t joins to the service_t table by account_products_t.obj_id0 = service_t.account_obj_id0 and account_products_t.service_obj_id0 = service_t.poid_id0. These are bi-directionally joined.

===================================================

That above paragraph addresses parent/child table relationships in BRM. But how do parent tables relate to other parent tables?

Parent tables are joined together by their poid_id0 columns.

Not all parent tables join to each other but when they do it will always be parent_table.poid_id0 = joined_parent_table._obj_id0.

For example, account_t and service_t are joined by account_t.poid_id0 = service_t.account_obj_id0

It is always easy to see the relationship in the tables by looking at the columns. Poid_id0, obj_id0, and anything that ends in obj_id0 (like account_obj_id0, service_obj_id0, etc) are the joined columns.

Wednesday

The Ten tips for Telephone Interviews

Source : SAPJOBS.COM


The Ten Commandments for Telephone Interviews

At James Rushmore Ltd, we have extensive experience in coaching people through interviews and we have compiled a unique guide to help you manage your next telephone interview.

The telephone interview will be shorter and may be more intensive than the face to face interview. The telephone interview is often arranged at the last moment allowing less preparation time, plus you will be interviewed through a medium that is renowned for its erratic behaviour.

However there are ten important steps that you can take to prepare for the telephone interview. A telephone interview is not an opportunity that should be wasted; that vacancy with an attractive salary and great benefits may just depend on how you handle yourself the next time the phone rings!

  • Arranging the Interview

When arranging the interview, pick a time when you have no pressing appointments. Probably 75% of all telephone interviews are up to 15 minutes late, a totally unacceptable number can be an hour or more late. You therefore need to schedule a time that will allow you to over run.

Steer away from arranging interviews in your coffee break or 20 minutes before another meeting. It is very important to sound unhurried and in control when you are speaking on the phone.

  • Morning or Evening?

Are you are morning or evening person? Try and arrange a time that suits your natural daily rhythm. This may prove more difficult to achieve with long distance calls.

Be aware of when you perform best and if your interview is scheduled for a natural ‘low’ time in your day, then allow yourself more free time around the interview to energise yourself.

  • Distractions

Make sure you will not be disturbed by your colleagues at work, or your family if you are at home. Make sure that your printer, PC or fax machine does not spring into vociferous life right in the midst of your call. If you are receiving the call on a standard phone, then also make sure your mobile phone or pager is switched off.

  • Allow the call to ring briefly

When the interview phone call come through, allow the phone to ring several times. This serves two useful functions -

First it allows you time to inhale deeply, calming your breathing and heartbeat. Your voice will sound better and warmer as a result.

Secondly, it allows the interviewer time to hear the phone ringing and thereby prepare themselves. One of the great unsolved mysteries of the phone system is it’s ability to ring at your end with out the caller realising. If you answer the phone on the first ring, the caller may not even know the call was connected! This can be a bad start to the most genteel of social calls, let alone an important telephone interview.

  • Answering the call

Answer with "Good morning/afternoon/evening,…..John Smith speaking."

It is very important to smile when you speak. It imparts confidence as well as adding a warm and friendly timbre to your voice. At the start of the conversation speak at a medium pace. The caller may be interviewing you in their second language, so you may need a little time to evaluate their fluency. As the conversation proceeds, be sure to match your speech to the pace and tone of the interviewer.

Speak directly into the phone, keep the mouth piece about one inch from your mouth. Be aware of any background noise that could be distracting for your interviewer. Another magical property of the telephone is it’s ability to pick up unwanted and embarrassing background sounds and amplify them to volumes far beyond the power of our own voice.

  • Listening

"No one listens, we all just wait for our turn to speak".

This is a very important point to remember during telephone interviews. As human beings, one of our weaker senses is our ability to collect information through our ears. Only some 15% of what we hear is actually retained. It is therefore vital in telephone interviews that your answers are kept factual and clear. The interviewer will only have their ears by which to judge you.

Ideally you should never take more than a 90 seconds to reply to any question. If it is a complex answer then break your answer in to 90 second segments. After each segment be sure to allow a break for the interviewer to respond. Remember long answers can be boring and you can easily talk yourself out of the running. Short, precise and digestible answers are the key to success.

  • The Rule of Three

Don’t be afraid to repeat your self three times in a subtle way.

A rule of thumb is :

"Tell them what you want to tell them;

Tell them;

And tell them what you told them".

However use this technique with the utmost discretion and creativity. No prizes will be awarded to those who simply repeat the same statement three times. Use this technique only for the key selling points in your interview.

  • Ask intelligent questions

Remember to ask questions as you go along. It will show you are interested and intelligent. Ask questions that can be answered relatively easily and quickly by the interviewer. This technique will make the interviewer feel positive about themselves and therefore positive about you.

Background research will pay dividends here. With the sheer quantity of the information on the Internet there can be no excuse for not asking a few informed and relevant questions.

  • Conference Calls

Conference calls pose additional problems over the one-to-one telephone interview. You may not know how many people are on the call at the other end, or if you are being broadcast through a loudspeaker.

Our advice is to treat the conference call as a series of one-to-one calls, making sure that you greet and handle each person in the same polite manner. You may not know the pecking order of the people on the conference interview, but they certainly will!

  • The Graceful Exit

Interviews can be misleading and signals can be so easily misinterpreted.

Never assume either that you have got the position, or that you have been rejected.

Be very positive about your self and your skills throughout the call. Your parting impressions should be ones of enthusiasm, competence and openness. Parting impressions are almost as important as opening impressions. Therefore smile when you say goodbye to leave the best impression.

The telephone interview is becoming increasing sophisticated with the wider introduction of video links. However the basic advice remains timeless and can be applied to whatever communication medium the world of technology throws our way.

Whether its a piece of copper cable or the very latest word in fibre optics there will always be a human being hanging on either end of it, striving to communicate with another member of species. Quiet remarkable when you stop to think about it!

Tip of the day : Finding a software Testing Job

here are many people who would like to get software testing jobs, but they are unsure about how to approach it. This may seem like a dream j...