How to record an approval process with QTP

In fact, this is according to your actual needs, there is no absolute definition of action, you must write one or more. Judging from your description, your approval process is designed to be a combination of multiple user actions, from a human perspective. But judging from this case, the connection between each action is relatively strong, and it would be better to use one action to do it.

However, if you have a lot of different interactions for each action, it may be better to write multiple actions. Because it may be more flexible to call.

This question is actually similar to designing a module of software, depending on your specific needs.

Qtp allows calls between actions, you can set an action to be called only by that script, or you can set it as a share action, so that it can be called by an external script. The convenience of using action is that you can easily control the input and output parameters of the action and how many cycles to run, all of which are directly set up in QTP with a graphical interface.

Another way is to make a function, you can also make a function module into the form of a function in the current action and be called repeatedly by the current action, or you can put the function in a library file or vbs file, and then you can set the location of these file sources in the resource settings of the script, so that multiple scripts can use the same function library.

How to split the script structure depends on your application and your actual needs.

Hello landlord!

Depending on your problem, you can continue with the recording, which is of course related to the program being recorded.

The landlord can split the recorded script into multiple actions, one action at a time, so that you can use the main action to call the ** you have recorded, which is also possible.

As for qtp just going through it, it must be that there is a problem with the running process of your script, and the landlord had better refine the problem to determine a better solution.

1.You can go on with the recording; But you have to pay attention to the cohesion.

2.Recording is simply documenting a process; After recording, you can add checkpoints to check whether the object is as expected (i.e. find bugs).

Recording is the most basic operation; And if you want to do a good job in test automation, it's not enough to just record; You need to learn to be descriptive and use a framework to implement it in conjunction with VBS.

Simple recording doesn't make any sense, you need to result in this qtp framework, code in expert view, then judge logic and so on.

Recording according to the steps of the use case is sufficient, and checkpoints can be inserted (set according to the expected result) after the recording is completed or during the recording. That's the simplest way to do it.

In addition, you can record each operation as a single action, and then call the action directly. This has a high rate of reuse. Convenient for later maintenance.

Recently, I am also studying QTP Q515770021. If you have a question, you will be able to communicate below.

Let's get started with qtp and then go to recording.

Can the question be more detailed? I'll give you a rough step:

1. Start QTP and select Web on the startup page.

2. Launch the browser.

3. Click the [Record] button and operate on the browser.

4. Turn off the recording, and then you can play it back.

You need to note that Step 1 and Step 2 must not be reversed.

This is because QTP recognizes the remote desktop as an object.

In fact, QTP does not recognize specific objects in the remote desktop, which is a limitation of QTP.

Actually, you can't use remote desktop qtp to record local IE operations. Not sure how you solved it.

What is the purpose of your test? Testing Remote Desktop?

This kind of test qtp is difficult to implement, qtp has its own object recognition mechanism, and you are beyond the scope of its implementation.

But if you have to do this kind of test, there should be a troublesome way. Record the actions to be performed by the remote machine in a script and save it on the remote machine. Then, create a qtp object on the remote machine through the createobject function, so that the qtp of the remote machine can be started locally and the script on the remote machine can be executed.

The main building is to strengthen the mastery of basic knowledge. Your input value needs to be dynamically fetched to make sense for testing.

Define the number of cycles.

You can use the getsheet method to dynamically assign a value to rowcount.

dim rowcount as integer

rowcount = "mysheet").getrowcount

for 1 to rownumbers

dialog("login").winedit("agent name:").set "mercury"

dialog("login").winedit("agent name:").type mictab

dialog("login").winedit("password:").setsecure "4b863a88710265f6236e7306d7be4db223f1ba84"

dialog("login").winbutton("ok").click

window("flight reservation").close

next

Add a for loop statement at the beginning and end.

Here's an example. dim iloop

for iloop=1 to 5

if iloop>4 then

exit for

endif === Add your ** here.

next Note: 1When actually using it, replace the number 5 with the number of times you want to cycle 2The above if statement is just an example, you can change the judgment after if, or change if iloop>4 then

exit for

The purpose of endif is to determine if the loop ends after 4 times, and stops executing to the 5th time.

Delete the entirety.

Select "Tools" "Internet Options" "Advanced" in IE and check the "Enable third-party browser extensions" option in Internet Explorer.

1. What you said about not being able to record is that there is no script after the page operation or the web object is not recognized?

If the web object is not recognized, there are two main reasons for this:

1) Incorrect selection of plugin when starting qtp. Since you said that you have selected a web plugin, this possibility can be ruled out.

2) You should start the browser before starting QTP, the wrong startup sequence will cause other reasons such as QTP installation errors, browser errors, system errors, etc. You can use Spy to identify web page objects before recording, and then make judgments based on the results. Also, take a look at whether bhomanager is enabled in the browser's management add-on.

2. I think this situation can only be explained as a machine or system failure, you can first determine which step is shut down through single-step debugging, whether it is the cause of QTP or the reason of the program under test.

The other is antivirus software, so try to close all antivirus software first.

Not all objects need to be produced by recording. You can scrape it yourself, modify the way of object description in 1, the qtp used is a cracked version, and you will often encounter a very depressing problem 2, the most helpless, similar to a plug-in.

I've also come across it a few times and have tried three of the available methods:

1 When you open QTP and prepare to record, remove the ActiveX plug-in, and then set it in QTP: tools->options->Action Screen->Advanced, select Load ActionX Controls, and re-open QTP recording.

2 Reinstall QTP and remember to save the recorded script. But this approach often leads to the recurrence of the problem.

3 You install 360, turn off 360, remove the related processes, reopen QTP, and start IE again, generally there will be no such problem.

Hope to help the landlord!

I have encountered two main situations:

1.Because the machine is equipped with 360, be sure not to start 360 and qtp at the same time, conflict;

2.Same as win7, need patch:; qtp_00626；qtp_00604；qtp 00651 and so on. Patches can be obtained from HP Support!

I suggest you xp+qtp11+ie7

or win7 64+qtp11+ie8

Or win7 32+

It is recommended to use IE7 or IE8, otherwise IE9 will not work well if you patch it.

Automation is a test function, but it is not compatible, which is stable and which is used!

QTP11 supports IE9 to be patched, if you don't want to patch, use IE8