I attended the presentations of new versions of Quality Center (QC) and QuickTest Pro (QTP) in the version 10.00. This HP in Issy les Moulineaux (Near to Paris – France) a rainy morning. And so, in the TGV (a very fast railway for the English) brings me back, I type this article to share with you the information provided by HP in their basement …
The celebration program was:
- New QC 10.00
- New BPT 10.00
- New QTP 10.00
- Method of pricing (on the licensing policy – a subject not treated here)
(Does the use of figures 10.00 warns that there will be many patch and it is expected to version 10.94 Only time will tell).
HP has reported that all the information and risk are subject to because not included in versions 10.00 in February. Yet I take the bet that if. This warning of HP is probably the only legal title.
I need not address in this article from Business Process T. (BPT) for the moment because it’s uncommon among French customers and above all a desire / wishes for HP to sell full containers (first desire of any software publisher after all).
Quality Center (QC) 10.00:
Regarding what Quality Center is, I refer you to my articles on tools for testing repositories / management as well as those on QC. The release date is scheduled for 31 January 09 and three packs will be distributed:
- QC Starter Edition: Designed for a team of 5 single-project
- Enterprise Edition QC: QC 9.2 equivalent current (TD for Quality Center)
- First Edition: Designed for a team with needs such as advanced multi-project, high availability platform supporting QC, etc.
I will detail here only the Enterprise Edition / First of QC because it is where the real changes / new features.
QC Enterprise Edition / First, the modules present:
- Requirements management
- Test plan
- Lab Tests
- Risk based testing
- Release management
- Defect management
- QA Lab Manager
The sentence shock input presentation by HP was "Mastering the chaos version requirements, tests and components”! Rather ambitious and shock, but see news (grouped by topic below).
Centralizing these unlike the current dashboard (9.2)
- New module replacing the dashboard
- Centralized reporting
- All panels are centralized in the module
- Creation of public view and private
- Report possible multi-project
- Take this version of reporting as the V1 from the old … Finalized dashboard module so.
Possibility to define a more complete test:
- Risks and technical occupations ==> assigned to a functional complex – calculation of risk
Versioning: this module is not useful for a small project
Version Management requirements, tests (test sheets for example) and components:
- Check-in and check-out
- Comparison between the
- Ability to return to a previous version
- Can be activated at a project through the hotel (the new business administrator, therefore)
- The versioning is of course to be taken into account before the project starts (part of best practices dear to CMMi and other ITIL)
- Establishment of baselines (creating a picture of a set of project components), to mark / identify the milestones of the project. Example: requirements validated V1: establishing a baseline. It also allows you to freeze a configuration of testing association with a test campaign.
- Guarantees to run the correct version vis-à-vis a test campaign
- Comparison of baseline possible ==> identifying the elements that have changed
QC Requirements Management:
- It would be a direct competitor tools like Doors, Req Pro and other Caliber
- HP cites a 2008 report issued by Forrester and noting that the new management module requirements of HP is the first before all others. Hmm … I just think this kind of premature conclusion since the version that comes out in February and that results can be obtained after a few months of intense use in the real customers. A monitor then.
- It is now (finally?) possible to define a project template and especially to use it and share it between many projects. The major fact is the possibility to update the template and distribute the update on the entire project implementing it. You should know that the current version 9.2 is only possible through internal development of each client.
- Ability to setup and maintenance of centralized template
- Broadcast "automatic" updates
- Maintenance of template by administrators
- Please note that this feature also joined the concepts of best practices advocated by CMMI and ITIL
- Output January 31
- WinRunner is no longer included in this pack
Contained in the pack Functional testing:
- Resource Management QTP:
- Tools Comparison
QuickTest Pro (QTP) 10.00:
- Monitoring local system: this module allows RUN when scripts to monitor the implementation and some points. Specifically we can identify at what point and following the action script a problem occurs. For example, a peak CPU load generated by the action of a QTP script. This will help to strengthen links and interactions between the teams test and those in charge of performance tests. It should be noted that this function has been implemented by many customers through internal development. They will appreciate.
- Improvement of the various GUI:
- Tools management tasks (TODO)
- Support for scripting
- Export to DOC format and PDF reporting
- Ability to attach screenshots
- Direct access to the script from QTP reporting
- Ability to compare two versions of scripts easily
My final impression is that QTP is transformed into CASE (Computer Aided Software Environment or AGL (Atelier de Genie Logiciel for French people)) but oriented tests. What I mean is that HP has incorporated many features to better script and more to help developers fully QTP scripts. I find it beneficial for all writers. Do not draw hasty conclusions and wait till the first returns of experience other than HP. Finally, synergy, linkages between QTP and QC seem also strengthened.
What about migration?
To migrate your versions to 10.00 you must already have version 9.0 (patch 26) and QC 9.2 (patch 12). Unable to migrate with older versions as these.
An upgrade tool is available on the HP site to help you with migration. But be careful if this works as the previous times you need to go through testing experts to help you because the migration tool from HP does not expect miracles and calls for the intervention of humans.
One last thing about the migration, if you go to QC 10.00 you should necessarily go to the 10.00 version of QTP.
Do we collect on the body of this bloodless automation testing tool that was a forerunner in our industry. He well-deserved retirement. Rest In Peace WinRunner and thank you for everything.
- It is no longer distributed with the pack functional testing
- End 2009: End of the developments and patch
- End 2011: The end
Goodies and “petits fours” (little cakes for corporate party in France):
And the goodies offered by HP for us to reward our time and attention? Well we had a pink plastic pen, a few blank sheets to the header of HP … and a book in English on the tests!
His name is "Optimize Quality for Business Outcomes – a practical approach to software testing" and this in its third edition. This is the first time I have heard of this book dealing with the tests. Below I list the main chapters:
1. What is the big deal about testing?
2. Testing the business requirements: start at the root of the problem
3. Test rules: build the backbone for effective testing
4. Test cases: let’s get down to the real stuff
5. Test optimization: balancing risk and effort
6. Why bother with non-functional testing?
7. Application security testing: the next frontier
8. Test sourcing: how outsourcing improves cost effective testing
9. Successful goal-driven approach KPI
10. Getting started: putting it all together
11. Appendix A – Common test techniques
12. Appendix B – HP application quality management solutions introduction and overview
13. Appendix C – Verification
14. Appendix D – Naming conventions
I try to read this book quickly and I will make my opinion, soon.
Ultimately, HP’s strategy is to play together in the editing software to expand its functional and its turnover. What is a healthy and able to provide end users with better service and services companies expanding their services (with a contribution of value added greater than today).
However, HP blithely tramples the toes of many competitors / software editor. So publishers with tools for managing requirements and configuration management / version will inevitably their market shares reduced inexorably by HP. As inexorable as desertification in Africa? Not so on this because, take for example publishers management software requirements, their products will not be dedicated more complete than that of HP. It remains to be seen more fully the choice of HP doing in this area and the effort to test them in real life!