Tuesday, 6 May 2014
Web Service Performance Metrics
• Server Side: can be gathered by stress testing on the server end.
Important parameters are:
– Server throughput (measured as the number of requests per second)
– Latency (time taken between the service request arriving and the request being serviced.)
• Client Side: client side monitoring or distributed load testing can be used to gather data. Important parameters are:
– Latency (WS processing time + network latency). This is the time taken for a service call to return the earliest response bytes
– Throughput (the average byte flows per unit of time, including latency)
– Error rate (identifies the dependability of the service)
Monday, 5 May 2014
Difference between single and double slash in Xpath
Answer:
/
/
- start selection from the document node
- allows you to create 'absolute' path expressions
- e.g. “/html/body/p” matches all the paragraph elements
- start selection matching anywhere in the docume
- allows you to create 'relative' path expressions
- e.g. “//p” matches all the paragraph elements
Sunday, 4 May 2014
Selenium Annotations
@Test
The annotation @Test identifies that a method is a test method.
Denotes a test method. Can be used with expected to assert expected results on the object under test.
@Before
Will execute the method before each test. This method can prepare the test environment (e.g. read input data, initialize the class).
Run before each test method is run i.e. do a setup
@After
Run after each test method is run i.e. do a teardown
Will execute the method after each test. This method can cleanup the test environment (e.g. delete temporary data, restore defaults).
@BeforeClass
Run before all the tests in a class (Runs once for all of the tests)
Will execute the method once, before the start of all tests. This can be used to perform time intensive activities, for example to connect to a database.
@AfterClass
Will execute the method once, after all tests have finished. This can be used to perform clean-up activities, for example to disconnect from a database.
Run after all the tests in a class (Runs once for all of the tests)
@Parameters
Allows you to run the same test with different data by defining the data parameters. @Parameters have to return List[], and the parameter will pass into class constructor as argument.
@RunWith
Exclusively tells the class that the Junit Test Case uses Parameterized runner
When a class is annotated with @RunWith or extends a class annotated with @RunWith, JUnit will invoke the class it references to run the tests in that class instead of the runner built into JUnit.
The annotation @Test identifies that a method is a test method.
Denotes a test method. Can be used with expected to assert expected results on the object under test.
@Before
Will execute the method before each test. This method can prepare the test environment (e.g. read input data, initialize the class).
Run before each test method is run i.e. do a setup
@After
Run after each test method is run i.e. do a teardown
Will execute the method after each test. This method can cleanup the test environment (e.g. delete temporary data, restore defaults).
@BeforeClass
Run before all the tests in a class (Runs once for all of the tests)
Will execute the method once, before the start of all tests. This can be used to perform time intensive activities, for example to connect to a database.
@AfterClass
Will execute the method once, after all tests have finished. This can be used to perform clean-up activities, for example to disconnect from a database.
Run after all the tests in a class (Runs once for all of the tests)
@Parameters
Allows you to run the same test with different data by defining the data parameters. @Parameters have to return List[], and the parameter will pass into class constructor as argument.
@RunWith
Exclusively tells the class that the Junit Test Case uses Parameterized runner
When a class is annotated with @RunWith or extends a class annotated with @RunWith, JUnit will invoke the class it references to run the tests in that class instead of the runner built into JUnit.
Friday, 2 May 2014
Why Cloud Testing
Traditional approaches to test a software incurs high cost to simulate user activity from different geographic locations.
Testing firewalls and load balancers involves expenditure on hardware, software and its maintenance. In case of applications where rate of increase in number of users is unpredictable or there is variation in deployment environment depending on client requirements, cloud testing is more effective.
Types of testing:
Steps for Cloud Testing
Testing firewalls and load balancers involves expenditure on hardware, software and its maintenance. In case of applications where rate of increase in number of users is unpredictable or there is variation in deployment environment depending on client requirements, cloud testing is more effective.
Types of testing:
- Stress Testing
- Load Testing
- Performance Test
- Functional Test
- Compatability Test
- Browser
- Latency
Steps for Cloud Testing
Jenkins master - slave configuration
- Start Jenkins Website and click on link ‘Manage Jenkins’. You will see following option among various other options.
Click on the above option which will take you to the following screen.
Thursday, 1 May 2014
Jmeter Blaze Meter Plugin
You can download blazemeter plugin from here you should locate it inside C:\jmeter\apache-jmeter-2.11\lib\ext
Open Jmeter and you will find blazemeter options
JMeter Cloud Test
These (paid/free) services are waiting for you, if you are using JMeter
BlazeMeter - don't mess around with building and managing your load testing servers. You can use this service to upload your existing JMeter scripts and resources (csv dataset files, etc) and run them from as many servers as you want, you pay for amount of servers/users you run over time and you can choose from which AWS locations to run the load test from. This service also provides nice central reporting capabilities
BlazeMeter - don't mess around with building and managing your load testing servers. You can use this service to upload your existing JMeter scripts and resources (csv dataset files, etc) and run them from as many servers as you want, you pay for amount of servers/users you run over time and you can choose from which AWS locations to run the load test from. This service also provides nice central reporting capabilities
Subscribe to:
Posts (Atom)