Skip to content

Releases: epam/Gepard

V4.0.35

04 Jul 21:22
Compare
Choose a tag to compare

Welcome to the first release of Gepard V4.x series!

There was a strong need to drift away from the old architecture (V3.x) that is fully based on JUnit 3, and was unable to handle new JUnit annotations and features.

Finally it is arrived, so enjoy the world of JUnit 4 and the extensions Gepard provides to you.

New features:

  • New module: gepard-rest that - among others - give connection possibilty to Jira.

Upgrade information from Gepard 3.x:

  • Must use Java 8
  • Test classes those extend CommonTestClass should forget that, rather implement GepardTestClass (actually no method needs to be implemented, as all has default implementation that should not be changed).
  • Test methods should be annotated with JUnit @test annotation
  • @TestParameter annotation removed for data driven test, use getDataDrivenTestParameter(id) method to access the test data
  • Timeout handling from old version is removed, from now on we can use @rule Timeout, @test(timeout), so what JUnit4 offers
  • As timeout handling is in JUnit's hand, no such info may be stored in testlist.txt files, therefore timeout related info should be removed from the existing testlist.txt files
  • See refactored example tests in gepard-examples module

For new test projects:

  • Use gepard-project-template-4.0.35.zip as starting point for a new test project.

Should you have any question, feel free to submit your mail to: https://groups.google.com/forum/#!forum/gepard-users

V3.2.31

02 Jul 20:42
Compare
Choose a tag to compare

In this release, several JUnit annotations those were unavailable till now become available, like @before, @after, @BeforeClass and @afterclass.

Seems this will be the last release of Gepard V3.x series, because by allowing these annotations, we reached the limit of the actual Gepard architecture, that is still using JUnit 3 core methods.
Feel free to upgrade to this release, and get prepared for the new V4.0 series that is on its way, and will use JUnit 4.

Use gepard-project-template-3.2.31.zip as starting point for a new test project.

Should you have any question, feel free to submit your mail to: https://groups.google.com/forum/#!forum/gepard-users

V3.2.22

12 May 09:43
Compare
Choose a tag to compare
  • added method: public Environment getEnvironment()
    to CommonTestCase, in order to reach environment variables easily.
  • Opera support removed (you may need a little more work if you would use that browser, that's all)
  • the necessity of lombok.jar for compiling Gepard was removed
  • refinements in cucumber and selenium modules, provide example on how to use cucumber+selenium together with Gepard (see gherkin/cucumber/selenium folder in examples)
  • Upgrade to Junit 4.12,
  • fix handling of @test annotation (from now on can be used within Gepard)
  • version increased, as core, selenium and cucumber modules updated and the new examples don't work with older versions

3.1.20 - New Module: gepard-selenium

13 Apr 09:14
Compare
Choose a tag to compare

Release Notes:

  • TEID (Test Environment ID) usage and consistency clarified/cleaned up (usage of TSID was eliminated)
  • system-under-test.version property usage and consistency clarified (application-under-test.version was removed). Because of this, get/setApplicationUnderTestVersion method renamed to get/setSystemUnderTestVersion
  • Environment is not static anymore, from the test you can reach it by calling getClassData().getEnvironment() method.
  • GepardDataFeeder interface init method changed (environment info added)
  • Gepard version set to 3.1 (because of the interface change, and the Environment access change)
  • introduce gepard-selenium module in order to offer easy usage of selenium (webdriver) with gepard-core
  • need lombok.jar (v 1.16.2) if you would like to compile it from source

Refer to this release in gradle build file in the following way:

dependencies {
    compile "com.epam.gepard:gepard-core:3.1.20"
} 

Use the project template file as starting point for your new project. Just extract it and execute
gradlew.bat run, and after the run, see reports in build/gepard-result folder.

NOTE FOR THOSE, WHO BUILDING IT FROM SOURCE:
1: If you build it from source, you may face with missing property value error. Either use latest source from the repo, OR you need to have gradle.properties file available for gradle, with the following content:

epmsepg_artifactory_repoKey=fakeRepoKey
epmsepg_artifactory_contextUrl=fakeContectUrl
epmsepg_artifactory_username=fakeUserName
epmsepg_artifactory_password=fakePassword

2: If you build it from source, you must install lombok.jar into your Java Compiler classpath. See more info on lombok here: http://projectlombok.org/
Have fun!

3.0.19

07 Apr 20:03
Compare
Choose a tag to compare

First open sourced release. See documentation here: http://epam.github.io/Gepard/

Refer to this release in gradle build file in the following way:

dependencies {
    compile "com.epam.gepard:gepard-core:3.0.19"
} 

Use the project template file as starting point for your new project. Just extract it and execute
gradlew.bat run, and after the run, see reports in build/gepard-result folder.

Have fun!