Очень часто в различных проектах присутствует необходимость в создании тестов на проверку производительности системы. Как правило, для реализации подобной задачи, специалистам необходимо создавать и описывать правила работы с приложением с нуля. В своем докладе я расскажу, как это можно упростить эту задачу, на примере использования инструмента для нагрузочного тестирования Gatling

1. 1
Integration performance tests
with existing test automation
framework using Gatling.
Shapin Anton
November 04, 2017

2. 2
Email: anton_shapin@epam.com
Skype: anton_shapin
GIT: http://github.com/kirlionik
Shapin Anton
Lead Software Test Automation Engineer.
Areas of my competency: manual, test
automation, performance and etc.
#
11+ years in IT.#
QA trainer at Epam.

3. 3
Agenda
Advertising Gatling.2
«Performance testing 101».1
«That's how awesome we are».3

4. 4
Agenda
#1
A high level Gatling introduction.#1
Questions.#3
Integration of performance testing
with an existing TAF.
#2

5. 5
LET`S START !

6. 6
GATLING
Gatling is a highly capable load testing tool. It
is designed for ease of use, maintainability and
high performance. It supports HTTP/S, JMS,
and JDBC protocols.
Gatling’s architecture is asynchronous as long as the underlying
protocol, such as HTTP, can be implemented in a non blocking way. This
kind of architecture lets us implement virtual users as messages instead
of dedicated threads, making them very resource cheap. Thus, running
thousands of concurrent virtual users is not an issue.

7. 7
GATLING
setUp(
scn.inject(
nothingFor(4 seconds),
atOnceUsers(10),
rampUsers(10) over(5 seconds),
constantUsersPerSec(20) during(15 seconds),
constantUsersPerSec(20) during(15 seconds) randomized,
rampUsersPerSec(10) to 20 during(10 minutes),
rampUsersPerSec(10) to 20 during(10 minutes) randomized,
splitUsers(1000) into(rampUsers(10) over(10 seconds)) separatedBy(10 seconds),
splitUsers(1000) into(rampUsers(10) over(10 seconds)) separatedBy
atOnceUsers(30),
heavisideUsers(1000) over(20 seconds)
).protocols(httpConf)
)

8. 8
GATLING
setUp(
scn.inject(
constantUsersPerSec(100) during(30 minutes)
)
).throttle(
reachRps(100) in (10 seconds),
holdFor(1 minute),
jumpToRps(50),
holdFor(2 hours)
)

9. 9
GATLING

10. 10
GATLING. PITFALLS.
The scripting language is Scala, with its own DSL.
Mixing Java and Scala in one project.

11. 11
Precondition
TEST LOGIC IMPLEMENTATION
TEST LOGIC / BUSINESS LOGIC
SERVICES
DATA BASESREST
SOAP
PAGE OBJECTS
Files and formats
(pdf, json, xml)
Configuration
Env. config
files
Others config
files

12. 12
Precondition
JAVA as a programming language.#1
MAVEN as a build tool.#3
JDK 1.8.#2
Modular approach in architectural designs.#4

13. 13
Integration performance tests
qa-test-config
qa-common-module
Acceptance tests
Performance tests
Use
Add module of performance tests
Gatling’s Maven Archetype allows you to integrate Gatling and run
it into your preferred IDE.

14. 14
Integration performance tests
qa-test-config
Environment configuration
files
Performance tests
qa-common-module
Endpoints
urls
Locators
Test data
generation
Pages
urls
Other useful utils

15. 15
Integration performance tests
Add Gatling Maven plugin into your “pom.xml” file
<plugin>
<groupId>io.gatling</groupId>
<artifactId>gatling-maven-plugin</artifactId>
<version>X.Y.Z</version>
</plugin>
<configuration>
<configFolder>src/test/resources</configFolder>
<dataFolder>src/test/resources/data</dataFolder>
<resultsFolder>target/gatling/results</resultsFolder>
<bodiesFolder>src/test/resources/bodies</bodiesFolder>
<runMultipleSimulations>true</runMultipleSimulations>
<simulationClass>performance.promo.simulations.BaseSimulation</simulationClass>
<noReports>false</noReports>
<propagateSystemProperties>true</propagateSystemProperties>
<failOnError>false</failOnError>
<jvmArgs>
<jvmArg>-DmyExtraParam=foo</jvmArg>
</jvmArgs>
</configuration>

16. 16
General structure of Gatling tests
Load profile
Section setUp of Simulation class.
Test logic /Business logic
Scenario object. It describes user
actions.
Test data generation
Java or Scala classes.
Http protocol configuration
Section HttpConf of Simulation
class.

17. 17
General structure of Gatling tests
Test data generation
Java or Scala classes.
@Component @Lazy
class VoucherCode @Autowired()(voucherSteps: VoucherTokensSteps, baseInfo: GeneralSteps) {
private val logger: Logger = LoggerFactory.getLogger(classOf[VoucherCode])
private val path: String = voucherSteps.getVoucherService.getPathVoucher
private val jsonListVouchers: List[String] = {
logger.info(s"Get list of json files with voucher codes")
val vouchers = voucherSteps.getJsonsForVoucherCodes(700, baseInfo.getDefaultUser)
JavaConverters.asScalaBufferConverter(vouchers).asScala.toList
}

18. 18
General structure of Gatling tests
Test logic /Business logic
Scenario object. It describes users
actions.
val scenarioVouchers = {
scenario("Applying voucher сodes")
.feed(buildFeeder(jsonListVouchers))
.exec(http("Applying voucher сodes")
.post(path)
.body(StringBody("${body}")).asJSON
.check(status.is(201))
)
}
private def buildFeeder(jsons:
List[String]) = {
(for (json <- jsons) yield Map("body" ->
json))
.toArray
.shuffle
}

19. 19
General structure of Gatling tests
Load profile
Section setUp of Simulation
class.
class TestSimulation extends Simulation {
setUp(
appValidVoucherCodes.scenarioValidVoucherCodes.inject(constantUsersPerSec(1)
during (2 minutes)),
appInvalidVoucherCode. scenarioInValidVoucherCodes.inject(constantUsersPerSec(1)
during (2 minutes))
).protocols(httpConf)
}

20. 20
Summary
1. This approach was tested on 3 projects and has
established itself as an effective one.
2. It’s a great tool for learning about performance testing.
3. This approach reduces the time to create and support
performance tests.
4. Enables easy integration of performance testing with CI
process.

21. 21
Thank you for attention!
Email: anton_shapin@epam.com
Skype: anton_shapin
GIT: http://github.com/kirlionik