Hp released a new tool named Unified Functional Testing which is a new tool that integrates two of HP’s Testing product in a common and IDE to provide a power-full testing framework for GUI and API testing:
You can find more information on our web, so please take a look.
•HP Service Test
•HP QuickTest Professional
To learn more check out my articles on:
Does HP sometimes leave you scratching your head in confusion? It’s definitely what happened to me when they announced their new HP Unified Testing Software product. I already have QTP 11 and Service 11.10, so I was left to wonder — was this a new and separate product??
As of now – as far as I can tell — it is not a separate, standalone product. If you log on to HP’s site and select Functional Test, what you are really doing is downloading QTP 11.
If you also want Service Test, it’s a separate download. My guess is that eventually HP will have an actual product named Functional Test that will possess the same functionality of QTP & Service Test in one standalone app.
So, my suggestion is, at least for now, is that when you hear “HP Unified Functional Testing software,” think “HP UFT” — a machine that has a standalone install of QTP Pro 11 with all add-ins, and a separate standalone install of Service Test 11.10 and you are using a Unified Functional Testing license.
Basically “Unified Functional Testing” (UFT) is a license type that allows you to integrate QuickTest Pro with Service Test.
“Unified Functional Testing” Version 1.0 license key supports Version 11.00 (and later versions) of QuickTest Professional (including its Add-ins) and Service Test. That means that if you want to be able to call QTP from ST (or vice versa) you’ll need a special license called UFT.
If you only have an “FT-Unified” license for QTP and ST, you will not be able to use the built-in integration ability of either product. So if you have a FT-Unified license and you select the ‘insertCall to Service Test Test’ menu option you will get the following message: “To insert a call to a Service Test test, QuickTest, you must be using a Unified Functional Testing license.”
Since this new license was most likely not included in the original HP licensing agreement, companies that currently hold an “enterprise License” will probably will be out of luck when it comes to using UFT.
A Unified FunctionalTesting license will look something like this:
RWEHKWHEKHWKEHKWJOEJOEFSJKSFJOE# “Unified FunctionalTesting” version “1.0”
a Functional Testing license will look like this:
HJHDJASHDJOEHAKFHADFJOEHKAFHKAS# “FT-Unified” version “1.0”
Notice why this is confusing — both have the word “Unified” in them – WTF!
Please – let me know if I’m not understanding UFT correctly.
UAT gives users the opportunity to see the system in action and is also a verification process that is used to see if the software works as expected.
There are many definitions of UAT, a very common one is:
Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers, or other authorized entity to determine whether or not to accept the system. (ISTQB Glossary V3.1)
UAT’s main objective is to verify if the system meets user demand and if it is ready for the market or for the production environment.
Here are 5 best practices to make the UAT process efficient:
Goto UnitedTest to know more.
It is crucial to identify the target audience and know them in depth, and understand what their problems and needs are. This way, there won’t be a waste of time on something that won’t work. In connection with users, it is important to select actual and potential users for UAT. The development team should not participate in the user test. The feedback that is obtained from users is very enriching since it allows them to see the errors and create future improvements.
Bonus tip: since the feedback obtained from the UAT is essential, the information must be clear and specific to generate optimum results. The best way to organize the data, during the process, is using a user acceptance testing checklist.
The Test Plan (sometimes also referred to as a QA Test Plan) can be seen as the instruction manual or guide for your testing effort. It describes the objectives of testing (what are you planning to verify and/or validate), the scope of testing (what will and will not be tested), together with the general and sometimes detailed schedule of the activities you want to perform (how and when are you testing).
It is advisable not to leave the User Acceptance Testing for the moment in which the software is about to be launched on the market.
Bonus tip: generate proper credentials for users and pretest the test cases to verify that they work well and that they make sense. If the tests are done remotely, the date and time must be scheduled for their execution and there must be adequate logistics so that everything flows according to plan.
A test case specifies the work procedure, expected results, and the conditions that a tester needs to verify. It is the basic documentation needed to determine if an application or one of its features is working as originally planned and desired.
A step-by-step plan is needed. This will serve as a guide for people during testing. This way, they will be concentrated in the right places. If the tests are done in person, it is recommended to print the guide to make the process easier for them. It is important to create test cases that are well detailed and that provide clarity to the process. Specify as much as possible, for example which button to click or what results to expect, among others.
Bonus tip: it is necessary to include negative test cases to know what happens in case the user does something unexpected, and in this way not only the best-case scenario will be reviewed.
It is important to know how to act when an error appears. When a bug is reported, as much information as possible should be recorded so that later it is easier to recreate the problem and solve it.
Bonus tip: use screenshots or screencasts to send bug data, they answer a lot of questions for a developer.
After the product is developed, it is necessary to have well-defined and clear acceptance criteria since they are the ones that decide if the product is approved or not.
Bonus tip: how to create an effective acceptance criteria? Keep these tips in mind:
Challenges in User Acceptance Testing Process
During the development of a product, companies can request changes whenever they want. They can even be changes requested at the last minute, which can hinder and delay the entire process. In these types of situations, it is necessary to make quick and timely decisions.
It often happens that the people chosen to perform UAT are not aware of existing business needs. They can also face a lot of technical problems during the test run. That is why it is recommended to verify that all team members are well informed and that there are trained staff available to assist them in case questions arise during the process.
As mentioned above, the UAT is performed at the last minute when there is little time for the product to go on the market. It is a critical and vulnerable period, so there must be planning, well-defined test cases, and a suitable test environment.
When communicating an error, there should be no ambiguity, everything that is communicated must be clear and simple, avoiding anything that interferes with the understanding of the situation. Clear communication should flow through the entire team.
In summary, UAT reduces the possibility of possible errors and increases the level of user satisfaction, which makes it an essential process to implement during the development of any product before it is launched on to the market. In addition to this, UAT helps save money, time, and frustration by ensuring end users will be satisfied with the final product.
More importantly, it is always more expensive to fix post-launch errors than previously detected. By conducting User Acceptance Testing, it can be ensured that the product is truly ready-to-market and there will be no sad surprises after launch.
For more information, please visit United Test.