com.hotels:heat-example-test-module

Parent POM for Hotels.com open source projects

License

License

GroupId

GroupId

com.hotels
ArtifactId

ArtifactId

heat-example-test-module
Last Version

Last Version

4.0.4
Release Date

Release Date

Type

Type

jar
Description

Description

Parent POM for Hotels.com open source projects
Project Organization

Project Organization

Hotels.com (Data Platform Team)

Download heat-example-test-module

How to add to project

<!-- https://jarcasting.com/artifacts/com.hotels/heat-example-test-module/ -->
<dependency>
    <groupId>com.hotels</groupId>
    <artifactId>heat-example-test-module</artifactId>
    <version>4.0.4</version>
</dependency>
// https://jarcasting.com/artifacts/com.hotels/heat-example-test-module/
implementation 'com.hotels:heat-example-test-module:4.0.4'
// https://jarcasting.com/artifacts/com.hotels/heat-example-test-module/
implementation ("com.hotels:heat-example-test-module:4.0.4")
'com.hotels:heat-example-test-module:jar:4.0.4'
<dependency org="com.hotels" name="heat-example-test-module" rev="4.0.4">
  <artifact name="heat-example-test-module" type="jar" />
</dependency>
@Grapes(
@Grab(group='com.hotels', module='heat-example-test-module', version='4.0.4')
)
libraryDependencies += "com.hotels" % "heat-example-test-module" % "4.0.4"
[com.hotels/heat-example-test-module "4.0.4"]

Dependencies

compile (7)

Group / Artifact Type Version
com.hotels : heat-bundle jar 4.0.4
com.github.tomakehurst : wiremock jar 2.17.0
ch.qos.logback : logback-classic jar 1.1.2
io.rest-assured : rest-assured jar 3.1.1
org.powermock : powermock-api-mockito jar 1.6.3
org.powermock : powermock-module-testng jar 1.6.3
org.powermock : powermock-module-junit4 jar 1.5.6

Project Modules

There are no modules declared in this project.

HEAT - User Documentation

Please, have a look here code of conduct

Table of Contents

WHY do we need a test framework

Do you ever need to write automatic tests on REST APIs? Welcome to our world! Well, there are a lot of commercial products used for that, and they work quite well.

But do you ever need to share your automatic scripts with other people all over the world or simply with other colleagues that need to make some changes in the same moment on the same code line as you? and do you ever need to commit your tests on a common repository? Do you? Good, and how do you manage all your merge tasks? Well, in this case maybe it would be useful go on with the reading....

The most famous commercial products you can find offer some fantastic GUIs that, in terms of "objects" to commit on a repository, are only one file. SoapUI, for example, is only an XML file. JMeter is a JMX file. All those files are made of several hundred of lines, and it is very difficult to see all the differences from a commit to another, and in case of merge, it can be very frustrating, especially if there are conflicts...

merge conflicts

So, in order to preserve your offices from unuseful and unproductive bloodshed, please look for other nice testing solutions! Do you need an idea? HEAT!

Back to TOC

HEAT - Hotels.com Engine Architecture for Testing

Heat is a simple solution based on REST ASSURED framework.

Typically you need a "test module" that, if driven in a proper way, has to produce requests to the application under test and has to receive responses from it. Then it has to make some checks on the retrieved response and to produce a documentation to show the user the result of the tests. This documentation has to be in a format readable and usable with a deploy manager like Jenkins (open source, so, folks, it wins!) or Atlassian Bamboo.

heat base architecture

What can change is "only" how you can drive your "test module".

Heat Test Framework makes everything very simple because you will be able to write test cases with a simple json file. So no need to write java code, no need to depend on developers for more complicated tests, no need to pay attention to our friend "checkstyle". It is a simple maven project with a pom linking to a "core" (open source) and a folder with your json files. Each json is a test suite and in each test suite there are several test cases. You can choose to run all the suites, only some of them, or only some test cases among the ones you have written with a command line.

heat detailed architecture

Back to TOC

Legal

This project is available under the Apache 2.0 License.

Copyright 2015-2018 Expedia Inc.

com.hotels

Hotels.com

Hotels.com open source contributions

Versions

Version
4.0.4
4.0.3
4.0.2
4.0.1
4.0.0
3.0.0
2.0.4
2.0.1
1.0.4