Thursday, 30 August 2012

QC: using Datatables within BPT Components

Here's a quick tutorial (with awesome mspaint screen-shot narrative assistance) on loading test data from an excel spreadsheet in to a QC/ALM BPT Component.

At a high level we add the data in to QC, associate the data with a test, and then use the data in the test. Read on for the breakdown on what this involves:

1)      Upload data to QC > Test Resource area, to a new asset termed ‘Data Table’ (don't ping me on the lack of variable naming consistency - this is just a rushed example).


a.       The data must be in the format where the data(/variable) name is across row 1, and the actual data values are contained on row 2
b.      I assume this is data driven (I have not tested this) meaning you could have data on rows 2, 3, 4, …, n, and this would just result in the test being called multiple times.


2)      In QC > Test Plan > Some Test > Parameters tab
a.       In Data Resource, locate your recently uploaded spreadsheet
b.      Add new test parameters
c.       Map parameters

That looks like:


3)      In your Test > Test Script tab
a.       Plug in your parameters here, but clicking on the iterations hyperlink




And now you’re done.


A note on QC/ALM11 behaviour. Ensure ‘Automatic Runner’ is closed and re-launched from Test Lab for data changes to be applied.

Thursday, 16 August 2012

Communicating with SCQA

A crucial aspect of any job is communicating your point of view clearly and susinctly. Putting words together to form and support an idea is a learnt and practised art.

People often ask me how I am so awesome at communicating. I have a technique which I always rely on. SCQA; simply break the message down on four points: the situation, complication, question and answer. This allows the reader (/listener) to understand your point of view nicely and easily.

So, what is the S, C, Q and A?

Situation
An overview/introduction in to what is going on

Complication
This is the climax, some tension or drama that really gets people going 'oh, that's not good'. Amount of drama to use obviously depends on the situation and your own agenda, don't over do it crying wolf.

Question
What can we do to resolve this?

Answer
You can lead the witness and help out with an answer.. Or you could structure the above three so that there is no option but what you're suggesting.


I should mention, the Q and A parts are optional. 


And voila, messaging made easy for the sender and receiver.

In example
S As you're aware TesterA has been allocated to two projects, C and as a result they have been unable to complete testing on ProjectX. Q Should we do something about this? A I suggest hiring a Project Manager who can count. It would make sense to have them assigned full time to ProjectX.

Yes, No, I don't know

There are three right answers to any question; yes, no and I don't know. It's intriguing how some people seem intent on using the wrong one for their situation. Perhaps it's a mask to cover not knowing everything.

Pro Tip: feel comfortable using each of these answers, and always use the right one; don't be a douche.

Robot Framework, Basic Setup

Plug: Robot Framework is quick to setup, easy to write tests for, and super fast to triage failures in. The last point really sets it apart...