Skip to content

Commit

Permalink
Changes for 5.0.4 version
Browse files Browse the repository at this point in the history
Switch to Selenium 4 and JDK 11
Implement several improvements:
 - Log should display system property value used during scenario
execution:
	Currently the log file displays only values for properties defined in
files read by ScenarioParametersManager. In certain circumstances it
could be interesting to know values of System properties and Environment
variables as well.
 - Add the possibility to print console output in a separated log file:
	Currently framework is writing full debug information in a log file
(usually debug_YYYYMMDDHHMMSS.log) and simply print output in standard
console. Although the print output is also written in the debug log
file, when running a scenario in a build it's not always easy to get the
console output.
	The purpose of this enhancement is to have the ability to also write
the print output in a separated log file which could be easily got after
a Jenkins or a Travis build run.
	Note that default behavior will be to have this functionality disabled.
Hence its introduction will be silent for users but they can activate it
if necessary in their corresponding builds.
 - Add CloseBrowsers annotation which closes all browsers for test and
step
 - Add sortListAndCompareEquality method to CollectionsUtil
 - Improve SpotTextTimeout.getCondition to use StringUtils.compare
 - Set DigitalizedVersion class public in StringUtils
 - Add filterXmlContent method to StringUtils
 - Print scenario properties usage in console at the end of execution
 - Make some Property and Counters classes and methods public
 - Add and tune some utilities
	+ Add MapUtil class with API to compare maps of strings
	+ Tune doc in CollectionsUtil and StringUtils
	+ Add readPropertiesFile(File) API method in FileUtil
	+ Add IsPartOf comparison to StringUtils
 - Add arrayToList API method on CollectionsUtil
 - Tune Application login when redirection occurred
Fix following issues:
 - ScenarioExecution fails to find the reason when a scenario execution
is stopped
	Sometimes we got following message in console: "For some unknown
reason, while shutting down, ScenarioExecution is not able to retrieve
the reason of the execution stop."
 - Bug in CollectionsUtil.sortListAndCheckEquality method
 - NaN error while displaying scenario counters
 - Tools QA Document title
 - Inaccurate time in message of SpotAbstractTimeout.wait(boolean)
method
 - Workaround for Selenium issue
SeleniumHQ/selenium#11750
 - API key or token stored in properties or environment variables have
their value exposed in log files
 - Bug select when using comparison pattern
 - Lowercase issue while reading tests parameter
  • Loading branch information
ffusier committed Jun 9, 2023
1 parent 26c29cd commit 27d0fcc
Show file tree
Hide file tree
Showing 48 changed files with 3,393 additions and 2,237 deletions.
6 changes: 1 addition & 5 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -30,9 +30,5 @@
########
**/screenshots/**
**/debug/**
**/launches/**

# RTC #
#######
.jazz5/**
.jazzShed/**
/.project
8 changes: 4 additions & 4 deletions pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
<modelVersion>4.0.0</modelVersion>
<groupId>com.ibm.bear.qa.spot</groupId>
<artifactId>spot-core-root</artifactId>
<version>4.3.1</version>
<version>5.0.4</version>
<packaging>pom</packaging>

<name>Root for SPOT Core projects</name>
Expand All @@ -20,15 +20,15 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.7.0</version>
<version>3.10.1</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
<release>11</release>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>3.2.1</version>
<executions>
<execution>
<id>attach-sources</id>
Expand Down
4 changes: 2 additions & 2 deletions spot-core-fwk/.classpath
Original file line number Diff line number Diff line change
Expand Up @@ -11,16 +11,16 @@
<attribute name="maven.pomderived" value="true"/>
</attributes>
</classpathentry>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.8">
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER">
<attributes>
<attribute name="maven.pomderived" value="true"/>
</attributes>
</classpathentry>
<classpathentry kind="src" output="target/test-classes" path="src/test/java">
<attributes>
<attribute name="test" value="true"/>
<attribute name="optional" value="true"/>
<attribute name="maven.pomderived" value="true"/>
<attribute name="test" value="true"/>
</attributes>
</classpathentry>
<classpathentry kind="output" path="target/classes"/>
Expand Down
3 changes: 3 additions & 0 deletions spot-core-fwk/.settings/org.eclipse.core.resources.prefs
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
eclipse.preferences.version=1
encoding//src/main/java/com/ibm/bear/qa/spot/core/nls/messages.properties=UTF-8
encoding//src/main/java/com/ibm/bear/qa/spot/core/nls/messages_fr.properties=UTF-8
13 changes: 8 additions & 5 deletions spot-core-fwk/.settings/org.eclipse.jdt.core.prefs
Original file line number Diff line number Diff line change
@@ -1,8 +1,11 @@
eclipse.preferences.version=1
org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.8
org.eclipse.jdt.core.compiler.compliance=1.8
org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
org.eclipse.jdt.core.compiler.codegen.targetPlatform=11
org.eclipse.jdt.core.compiler.compliance=11
org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
org.eclipse.jdt.core.compiler.problem.enablePreviewFeatures=disabled
org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
org.eclipse.jdt.core.compiler.problem.forbiddenReference=warning
org.eclipse.jdt.core.compiler.problem.reportPreviewFeatures=ignore
org.eclipse.jdt.core.compiler.release=disabled
org.eclipse.jdt.core.compiler.source=1.8
org.eclipse.jdt.core.compiler.problem.reportPreviewFeatures=warning
org.eclipse.jdt.core.compiler.release=enabled
org.eclipse.jdt.core.compiler.source=11
31 changes: 10 additions & 21 deletions spot-core-fwk/pom.xml
Original file line number Diff line number Diff line change
@@ -1,15 +1,13 @@
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>com.ibm.bear.qa.spot</groupId>
<artifactId>spot-core-root</artifactId>
<version>4.3.1</version>
<version>5.0.4</version>
</parent>
<groupId>com.ibm.bear.qa.spot</groupId>
<artifactId>spot-core-fwk</artifactId>
<version>4.3.1</version>
<version>5.0.4</version>
<name>Core of the SPOT framework</name>

<dependencies>
Expand All @@ -21,27 +19,18 @@
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-java</artifactId>
<version>3.14.0</version>
<version>4.6.0</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-http-jdk-client</artifactId>
<version>4.6.0</version>
</dependency>
<!-- ActiveMQ -->
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-broker</artifactId>
<version>5.15.14</version>
<version>5.17.2</version>
</dependency>
</dependencies>

<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.7.0</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
</plugins>
</build>
</project>
Loading

0 comments on commit 27d0fcc

Please sign in to comment.