Releases: Frameworkium/frameworkium-core
Releases · Frameworkium/frameworkium-core
Frameworkium 2.0.10
Major Changes
Client breaking changes
- None
New/Improved Functionality of Note
- Support for AngularJS 2. If its used, it will automatically detect it and apply the correct waits.
Minor Changes
- The BasePage method "waitForAngularRequestsToFinish()" has been refactored to "waitForJavascriptFrameworkToFinish()"
Frameworkium 2.0.9
Major Changes
Client breaking changes
- None
New/Improved Functionality of Note
- Now allows Chrome User Data Directory to be passed in, for specifying custom chrome profiles. Pass
-DchromeUserDataDir=/blah/blah/blah
as a param to utilise
Minor Changes
- None
Frameworkium 2.0.8
Major Changes
Client breaking changes
- None
New/Improved Functionality of Note
- Fixed issue #39
Minor Changes
- None
Frameworkium 2.0.7
Major Changes
Client breaking changes
- None
New/Improved Functionality of Note
- Fixed issue #37
Minor Changes
- Updated ngwebdriver version
Frameworkium 2.0.6
Major Changes
Client breaking changes
- None
New/Improved Functionality of Note
- Improved issue where final screenshot wasn't being sent to capture
Minor Changes
- Updated BaseTest loggers to use
this
rather thanBaseTest
meaning more specific logging messages - Updated log4j and jackson-annotations to latest
- Minor refactorings
Frameworkium 2.0.5
Major Changes
Client breaking changes
- None
New/Improved Functionality of Note
- Updated to Selenium 2.53.1 which should now work with Firefox 47.0.1
Minor Changes
- Updated Spock version.
Frameworkium 2.0.4
Major Changes
Client breaking changes
- Moved frameworkium repositories to Frameworkium, a new github organisation
- Changed maven groupId to
com.github.Frameworkium
, please now use:
<dependency>
<groupId>com.github.Frameworkium</groupId>
<artifactId>frameworkium-core</artifactId>
<version>2.0.4</version>
</dependency>
New/Improved Functionality of Note
- Fixed bug from 2.0.3 which encountered an error when using Capture with a
BeforeClass
method when usingconfigureBrowserBeforeUse()
Minor Changes
- Updated
README.md
Latest Stable
Frameworkium 2.0.3 Release Note
Major Changes
Client breaking changes
- None
New/Improved Functionality of Note
- Added
RetryFlakyTest
class which has a default of 1 retry that can be configured by using the following:-DmaxRetryCount=2
- Fixed bug from 2.0.2 which ignored config file specified with:
-Dconfig=xx.yaml
Minor Changes
- Updated
README.md
Latest Stable
Frameworkium 2.0.1 Release Note
Major Changes
Client breaking changes
- Renamed
AwaitedConditions
toExtraExpectedConditions
to improve IDE support - Removed
__stepStart(String)
and__stepFinish()
from APIBaseTest
- Use
AllureLogger.stepStart(String)
andAllureLogger.stepFinish()
instead - Methods in UI
BaseTest
will be removed for release 2.1
- Use
New/Improved Functionality of Note
- Fixed bug whereby filtering tests cases using JIRA JQL failed
- Fixed bug where
visibility
inBasePage
wasn't updated to reflect timeout passed in fromPageFactory.newInstance(Class<T> clazz, String url, long timeoutInSeconds)
when usingBasePage.get(String url, long timeout)
- Fixed inclusion of
-Dthreads
into the allure environment section and added-Dconfig
- Added
configureBrowserBeforeUse()
toBaseTest
- This is enables the use of
@BeforeClass
methods for test class setup - Simply call
configureBrowserBeforeUse()
to initialise the browser
- This is enables the use of
Minor Changes
- Moved to travis-ci.org for CI
- Added more unit tests to help prevent bugs
- Switched to the
1.4.x
branch ofallure-testng-adaptor
as it seems more recently active than1.5.x
- Updated
jackson-annotations
- Removed test scope restricton for
groovy-all
; it is needed by rest-assured and others
Major New Release
Frameworkium 2.0.0 Release Note - now with REST API testing
Major Changes
Client breaking changes
- Change Java package structure, notably:
pages.internal.BasePage
->core.ui.pages.BasePage
pages.internal.Visible
->core.ui.annotations.Visible
pages.internal.Invisible
->core.ui.annotations.Invisible
tests.internal.BaseTest
->core.ui.tests.BaseTest
pages.internal.PageFactory
->core.ui.pages.PageFactory
- Enforced only one Visibility related annotation per field i.e. one of
@Visible
,@Invisible
,@ForceVisible
- Enforced only one Test ID Annotation
- Either
@TestCaseId
or@Issue
- Either
- Upgraded to RestAssured 3.0.0, see release notes for details
- Updated AspectJ to 1.8.9 (clients need to update
aspectj.version
in your frameworkiumpom.xml
)
New/Improved Functionality of Note
- Rewrote Visibilty annotation parsing code:
- Visibility annotations now work with
WebElement
,HtmlElement
,TypifiedElement
andList
s thereof.
- Visibility annotations now work with
- Introduced
@ForceVisible
annotation. This should only be used as a last resort when trying to make visible an element that is occluded or not displayed - Added Visibility class
- e.g. inside a Page
visibility.forceVisible(element)
or inside an HtmlElement componentnew Visibility().forceVisible(element)
- e.g. inside a Page
- New PageFactory method for specifiying timeout
- e.g.
PageFactory.get(Page.class, 60)
orPageFactory.get(Page.class, "http://url", 60)
- e.g.
- Updated ngWebDriver and added method
waitForAngularRequestsToFinish()
toBasePage
for use in page objects where necessary - Send screenshots to Capture asynchronously i.e. no longer block test execution.
- Added support for Marionette, use
-Ddriver=Marionette
- REST API testing
- Added new
BaseService
andBaseTest
for API testing, for examples see the frameworkium repo.
- Added new
Minor Changes
- Removed Eclipse Formatter
- Updated all dependences to latest versions
- Improved logging
- Utilised more Java 8 goodness e.g. Streams and lambdas
- Added tests to core to help prevent introduction of bugs