Lr_ testing strategy (single scene, mixed scene)

 

We assume that the nine business test scripts written, we have two kinds of test strategy:

1, mixed scene (mixed business), which is running this put together nine business

2, a single scene (single business), which is running a business a business.

Generally the first single mixing scene scene, the scene is generally a single purpose is to find the defect, found bottlenecks. The scene is mixed assess the overall system performance.

Such as the acceptance of a project, let you to evaluate how the overall performance of the system, this time to do is to test the hybrid scene.

You can start and single, the processing capacity of each module to see what it is like, single-system scene generally means we may have a problem.

 

A start and post messages (without attachments), before the script pitted a good idea to run it, we are in vugen a user on the run. After the operation to see if run successfully.

Determine business success did not succeed, not in the non-test result Inside, it is possible that he would not show up, the most accurate is to look at the project, send a message have not been successful, or to look inside the database.

Next postings to run this module. Post this business module contains:

Open the home page, login, select a module, point to submit post

Open Home is not logged in, it is to open the home page and login is not necessarily a relationship.

 

Put controller running inside an hour expectation Posts 150,000, but the result made 100,000, it is not to say that post messages did not meet our performance requirements?

Can not. There are home, login, login is slow because it will lead to postings very slow, is made in a relatively small time posts would amount, because it is one hour Mody, put a lot of time allocated to the login above.

If we want to put our focus postings go up, you want to see the post, others do not want to focus on, then we will weaken log in, for example, log on to run once, run postings 10,000, or log on to run only once, others We ran postings.

So if you want to see which module in question did not put the other modules weaken, the pressure bearing down on the module you want to see.

For example, we only want to submit a post test this step, non-stop crazy submit a post, then we can submit to step in front of the posts are thrown int inside, or add another action, log in once made 100 posts. . Throw int, long time may fail.

 

To select a module from true we started doing this performance test.

We did a random selection module, random postings

We can add a lot of action, left, right, point Create New Action

 

Then we can copy the code to open the home page of the new action for the index inside; from there into the login log on to refresh the page. The remaining option is a module, the postings.

 

Parameters are global variables are private. Open the home front fids other parameters in the script in action also can be used.

 

From the beginning of the script design scene

1) disposed about the execution order, the set point run, Run Logic, movable up and down.

2)Insert Block

If you want to control the index, login only run once, Action run many times, can point to Insert Block, the management is doing, Run this is a Block, block.

 

3), move to Block the following, the delete action. Select Block0, point insert action, put into Block in Action

 

4) Block property

index, login to run once, at the point I Block0 property, you can set it to run how many times Block0. For example, write 100 times, I write the equivalent of a for loop.

I suppose this script 10 iterations, the number of posts that should be made: 1000, log in 10 times.

We are now to set up a simple point home, login, post all Xianpao 1.

Guess you like

Origin www.cnblogs.com/fanf/p/12659921.html