When things slip, a typical reaction is to add processes especially for tracking and monitoring. Just take the overhead effort for effort tracking for example. I’ve been in a lot of projects that at one point or another have gotten so delayed. A knee-jerk reaction is to have the team prepare more reports — daily status updates from everyone, summarized daily progress reports from the leads, reports for upper management, reports for client, etc, etc. This has its benefits — it provides more visibility on what’s going on in the project, and it can pacify stakeholders since it gives the impression that you’re on top of things. What it doesn’t do is get more of the actual needed work done. It doesn’t get more work coded. It doesn’t get more tests executed.
Instead of just diving into the “more reports” bandwagon, what I’d like is for the team to look into how we’re currently doing. What’s working for us? What isn’t? What do we need to do differently? These are questions that usually get asked in a retrospective meeting. If we google “retrospective”, a definition that turns up is “looking back on or dealing with past events or situations”. Reflecting on what has happened is but a part of it. In retrospectives, you also try to identify what you need to bring forward to keep your project successful or to recover so that your project will (hopefully) be successful.
I think I can pretty much go ahead and do a little retrospective on my own. We all can do it individually. But that just won’t suffice. I can plan all I want but if the folks who will execute are not aligned with the plan, then the plan will just fail to materialize. And you can come up with all brilliant sorts of ideas and workarounds but if you can’t get the other guy to execute then it wouldn’t matter so much (but I’ll credit your brilliance, of course). Retrospectives need to be a team thing. WE need to come up with plans for improvement that WE are ALL willing to execute or follow through. In the end, there is no one else to drive the project’s success but US as a team.
I stumbled upon this deck again and it’s really something that I want to share to the younger ones. Time management wasn’t exactly something I learned when I was starting out. I came from projects where OT would become the norm at certain points, and we even had Saturday work. I was so time-poor. As I grew older, I came to realize how valuable my time is. How I could make up for losses for some things, but I can never get back time I have lost or wasted. And that the more efficiently I manage my time will allow me to spend it on things that matter more.
Saved myself some time by not writing my own presentation covering the same topic.
One of the points I like is #18 which had a quote from Jason Cohen (@asmartbear):
Only ever work on the thing that will have the biggest impact.
I think most especially for the younger ones, we often get sidetracked by initiatives or other non-project related tasks. We fill up our plate with a lot of things. We say “yes” to this and that. But then you have to think about it, step back and look at the big picture, and reflect whether the things that you are doing are really the things that you need to grow or achieve your goals. As an aspiring tester/technologist, are these tasks really relevant to making myself more technical and capable in my craft?
We’re three weeks in our current project. I know it’s still a period of adjustment for you. You have a lot to take in, and I’ve been asking you to do stuff that is new to you. I know things can be a bit difficult at first. You might feel overwhelmed. You might just want to curl up into a fetal position, hug your favorite stuff toy, and just wish everything away. I know, I’ve been there. And I’m here to tell you to not despair.
Sometimes it’s the fear of having to do something big that freezes us into inaction. We end up not accomplishing anything because our minds are too caught up at the scope of what we have to accomplish.
It is not because things are difficult that we do not dare, it is because we do not dare that they are difficult. ~ Seneca
When you feel like there’s too much in your plate, here’s what you can do. Take a step back, breathe in, breathe out. Don’t try to tackle everything at once. That’ll just be crazy. Find out what you need to prioritize at the moment, then focus on those. Try to break up the work into smaller bite-sized portions. Taking it one step at a time will make it less stressful and less daunting for you. Sometimes it’s just hard to get the ball to start rolling, but once kicked off, things get easier as you go along.
When you feel like you’re sinking, do not hesitate to call out for help. You must remember that you are not alone in this project. Your team mates are here, we’ve got our senior test automation engineer (Sr. TAE), and I am here (I’m not just a pretty face, you know). We also have support from our team leads and our manager. Don’t take asking for help as a sign of defeat or something that will be taken against you. That may be the case in other cultures or other teams, but I assure you that it’s not the case with me. But don’t take this as a cue that you can just ask for help anytime and every time. What I’d want is for you to learn how to help yourself first. And if you come to the point when you’re already doing your best and things are still not working out, that is when you reach out.
So there. I hope you don’t feel too overwhelmed. Know that you can rise above that feeling and that you have my support.
In the end, everything will be okay. If it’s not okay, it’s not yet the end. ~ Fernando Sabino, translated from Portuguese
The past couple of days of our QTP training covered a lot more ground. The most nifty stuff are on tools like the Object Repository, the Object Spy (which is an icon of a guy with a top hat reminding me of Professor Layton), the Active Screen, and the topics on parameterization. I created a short video covering the last 2 topics. So there I demonstrate two things:
- Updating the script with the help of Active Screen — instead of having to record all over again
- Updating the script to make use of parameters instead of the hard-coded values.
For our Application Under Test (AUT), we made use of the sample application called “Flight” which was bundled with QTP. We were given the test script that we had to automate. Essentially, the script involved:
1. Logging in
2. Creating an Order
3. Faxing an Order
4. Logging out
To accomplish this, here are the basic steps:
(1) Create a new test by selecting File -> New -> Test from the menu (or CTRL+N).
(2) Update the Record and Run Settings by selecting Automation -> Record and Run Settings… from the menu. We needed to add our AUT in the list of Applications.
(3) Create the script — including steps, checkpoints and output values.
You can try recording the steps and it will be able to produce a script. However, playing it back will fail due to some hard-coded items that are no longer applicable upon rerunning (e.g., window title included the Order Number which would be different in the next run). It also wouldn’t have the needed checkpoints (or the test/assertions) and it wouldn’t gather output data.
For the first script created, QTP’s record function was used to record the steps. Inserting checkpoints and output values were also done during the recording. For instances wherein the object title or text being checked is dynamic (e.g., window title containing the Order Number), we made use of regular expressions e.g., instead of “Flight No. 19″ as originally recorded, we made use of “Flight No.*” with the regular expressions checkbox marked.
Here’s a link to a video recording of the script creation: http://youtu.be/DwayCg1M5IY
Alternatively, here’s a similar script creation video without step 3 though, but it does have audio. It covers basic recording and inserting checkpoints and an output value.
Earlier today was Day 1 of a 5-day Basic QTP Training that I’m attending at work. Putting my notes here just in case I have to relearn or I have to echo the training. So initially, we did some setup (see details below), and then there was a demo where a manual test case was automated (will post this separately).
Install HP QuickTest Professional
This involved an installer that was nearly 4GB in size. The setup with the wizard was pretty straightforward. After installing, additional configuration included specifying the license and going to Tools -> Options to modify the Run settings such that the “Allow other HP products to run tests and components” checkbox is marked. This is probably since we’re integrating with HP ALM.
Set up ALM integration
QTP can manage to work on its own, but since we plan to be working with ALM for storing and managing the tests we had to install the following items:
- ALM Explorer (ALMExplorerAddIn.msi, alternative to viewing ALM in IE)
- HP Quality Center Connectivity (TDConnect.exe, an ALM add-in)
- QTP for Business Process Testing (Quick-Test_Add-in_for_ALM-QC.msi)
An interesting find… Capgemini, Sogeti and HP co-sponsored the 5th edition of the World Quality Report.
It examines the current state of application quality and testing practices across the globe, as well as emerging trends that may affect the future of testing within the next two years.
The report is available at http://www.hp.com/go/capgemini or at http://www.worldqualityreport.com/.
On page 9 of the 64-page report, it lists the following recommendations:
- Improve reporting of business-oriented metrics to demonstrate the value of QA
- Innovate and optimize QA operations for return on investment
- Establish a specialized function for mobile testing
- Make greater use of the cloud for testing
- Establish test environment and test data management practices
- Integrate testing into agile projects
Last week, a teammate posted a question in the forums asking for a way to extract a report from ALM that will list the test cases and the requirements that they are linked to. So although, there are probably built in reports, I figured that this is something that could also be extracted via an SQL query in the dashboard.
Here’s the query I came up with:
SELECT --REQ.*, TEST.*
WHERE REQ_COVER.RC_REQ_ID = REQ.RQ_REQ_ID
AND REQ_COVER.RC_ENTITY_ID = TEST.TS_TEST_ID
AND REQ_COVER.RC_ENTITY_TYPE = 'TEST'
ORDER BY TEST.TS_TEST_ID
Another team mate shared a link to a similar forum topic where someone had already posted a similar query. The query in the other answer has the following additions:
- It includes a join to ALL_LISTS on all_list.al_item_id = test.ts_subject — perhaps to filter by folder
- It includes a join to REQ_TYPE on req_type.tpr_type_id = req.rq_type_id — perhaps to filter by requirement type
TIL that Excel has this thing called “Sparklines” where you can have a mini-chart or visualization of your data in as small a space as a single cell. I made samples of the 3 types of Sparklines (Line, Column, and Win/Loss) captured in the image below. In each of the table, the last column displays the sparkline created for the data in the same row.
The Sparklines thingy is available from the Insert menu of the Excel Ribbon.
We currently have a SharePoint 2010 List wherein we expect members of the team to enter their records, but at the same time we wanted to be able to score their entries. The downside is, with the default settings of the list, the score field is also available to the rest of the team and so they can revise their own scores. After a bit of googling, I found a solution that works. It involves creating new forms and conditional formatting using the SharePoint Designer. The end result was that if the owner of the list accesses the forms, the Score field is displayed; and it is hidden otherwise.
The summary of steps are as follows, but the more detailed steps are in the file attached.
- Open your list in the SharePoint Designer.
- Create new forms for new, edit and display modes, and set these as the default forms.
- Edit each of the custom forms you created – enclose the section that you want to hide in this tag:
- Save your changes.
I used the permission mask “2048″ as it corresponds to the permission to Manage Lists. Other parameters can be found in the second link under references below.