mirror of
https://github.com/Alfresco/alfresco-community-repo.git
synced 2025-07-24 17:32:48 +00:00
496 lines
23 KiB
Markdown
496 lines
23 KiB
Markdown
|
||
|
||
:paw_prints: Back to [TAS Master Documentation](https://gitlab.alfresco.com/tas/documentation/wikis/home)
|
||
|
||
---
|
||
## Table of Contents
|
||
* [Synopsis](#synopsis)
|
||
* [Prerequisite](#prerequisite)
|
||
* [Installation](#installation-if-you-want-to-contribute)
|
||
* [Package Presentation](#package-presentation)
|
||
* [Sample Usage](#sample-usage)
|
||
* [How to write a test](#how-to-write-a-test)
|
||
* [How to run tests?](#how-to-run-tests)
|
||
* [from IDE](#from-ide)
|
||
* [from command line](#from-command-line)
|
||
* [Perform CMIS Queries](#perform-cmis-queries)
|
||
* [Listeners](#listeners)
|
||
* [Test Results](#test-results)
|
||
* [Test Rail Integration](#test-rail-integration)
|
||
* [Configuration](#configuration)
|
||
* [How to enable Test Rail Integration?](#how-to-enable-test-rail-integration)
|
||
* [Change Log](docs/CHANGELOG.md) :glowing_star:
|
||
* [Reference](#reference)
|
||
* [Releasing](#releasing)
|
||
* [Contributors](#contributors)
|
||
* [License](#license)
|
||
|
||
## Synopsis
|
||
|
||
**TAS**( **T**est **A**utomation **S**ystem)- **CMIS** is the project that handles the automated tests related only to CMIS API integrated with Alfresco One [Alfresco CMIS API](http://docs.alfresco.com/5.1/pra/1/topics/cmis-welcome.html).
|
||
|
||
It is based on Apache Maven, compatible with major IDEs and is using also Spring capabilities for dependency injection.
|
||
|
||
As a high level overview, this project makes use of the following functionality useful in automation testing as:
|
||
* reading/defining test environment settings (e.g. alfresco server details, authentication, etc.)
|
||
* managing resource (i.e. creating files and folders)
|
||
* test data generators (for site, users, content, etc)
|
||
* helpers (i.e. randomizers, test environment information)
|
||
* test logging generated on runtime and test reporting capabilities
|
||
* test management tool integration (at this point we support integration with [Test Rail](https://alfresco.testrail.net) (v5.2.1)
|
||
* health checks (verify if server is reachable, if server is online)
|
||
* generic Internal-DSL (Domain Specific Language)
|
||
|
||
Using Nexus -Release Repository, everyone will be able to use individual interfaces in their projects by extending the automation core functionalities.
|
||
|
||
**[Back to Top ^](#table-of-contents)**
|
||
|
||
## Prerequisite
|
||
(tested on unix/non-unix distribution)
|
||
* [Java SE 1.8](http://www.oracle.com/technetwork/java/javase/downloads/index.html).
|
||
* [Maven 3.3](https://maven.apache.org/download.cgi) installed and configure according to [Windows OS](https://maven.apache.org/guides/getting-started/windows-prerequisites.html) or [Mac OS](https://maven.apache.org/install.html).
|
||
* Configure Maven to use Alfresco alfresco-internal repository following this [Guide](https://ts.alfresco.com/share/page/site/eng/wiki-page?title=Maven_Setup).
|
||
* Your favorite IDE as [Eclipse](https://eclipse.org/downloads/) or [IntelliJ](https://www.jetbrains.com/idea).
|
||
* Access to [Nexus](https://nexus.alfresco.com/nexus/) repository.
|
||
* Access to GitLab [TAS](https://gitlab.alfresco.com/tas/) repository.
|
||
* GitLab client for your operating system. (we recommend [SourceTree](https://www.sourcetreeapp.com) - use your google account for initial setup).
|
||
* Getting familiar with [Basic Git Commands](http://docs.gitlab.com/ee/gitlab-basics/basic-git-commands.html).
|
||
* Getting familiar with [Maven](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
|
||
* Getting familiar with [Spring](http://docs.spring.io).
|
||
* Getting familiar with [TestNG](http://testng.org/doc/index.html)
|
||
|
||
**[Back to Top ^](#table-of-contents)**
|
||
|
||
## Installation (if you want to contribute)
|
||
|
||
* Open your GitLab client and clone the repository of this project.
|
||
* You can do this also from command line (or in your terminal) adding:
|
||
|
||
```bash
|
||
$ git clone https://gitlab.alfresco.com/tas/alfresco-tas-cmis-test.git
|
||
# this clone will have the latest changes from repository. If you want to checkout a specific version released, take a look at the [Change Log](docs/CHANGELOG.md) page
|
||
$ cd alfresco-tas-cmis-test
|
||
# this command will checkout the remove v1.0.0 tagged repository and create locally a new branch v1.0.0
|
||
$ git checkout tags/v1.0.0 -b v1.0.0
|
||
```
|
||
|
||
* Install and check if all dependencies are downloaded
|
||
|
||
```bash
|
||
$ mvn clean install -DskipTests
|
||
# you should see one [INFO] BUILD SUCCESS message displayed
|
||
```
|
||
**[Back to Top ^](#table-of-contents)**
|
||
|
||
## Package Presentation
|
||
|
||
The project uses a maven layout [archetype](https://maven.apache.org/plugins-archives/maven-archetype-plugin-1.0-alpha-7/examples/simple.html):
|
||
```ruby
|
||
├── pom.xml
|
||
├── src
|
||
│ ├── main
|
||
│ │ └── java
|
||
│ │ └── org
|
||
│ │ └── alfresco
|
||
│ │ └── cmis
|
||
│ │ ├── (...)
|
||
│ │ ├── CmisProperties.java #handles all properties from default.properties
|
||
│ │ ├── CmisWrapper.java #wrapper around CMIS API
|
||
│ │ └── exception
|
||
│ │ └── (...)
|
||
│ ├── test
|
||
│ │ ├── java
|
||
│ │ │ └── org
|
||
│ │ │ └── alfresco
|
||
│ │ │ └── cmis
|
||
│ │ │ ├── CmisDemoTests.java #demo example
|
||
│ │ │ └── CmisTest.java #abstract base class that should be inherited by all tests
|
||
│ │ └── resources
|
||
│ │ ├── alfresco-cmis-context.xml #spring configuration
|
||
│ │ ├── default.properties #all settings related to environment, protocol
|
||
│ │ ├── log4j.properties
|
||
│ │ └── sanity-cmis.xml # default suite of tests
|
||
```
|
||
|
||
**[Back to Top ^](#table-of-contents)**
|
||
|
||
## Sample Usage
|
||
|
||
Following the standard layout for Maven projects, the application sources locate in src/main/java and test sources locate in src/test/java.
|
||
Application sources consist in defining the CMIS object that simulates the API calls.
|
||
The tests are based on an abstract object: CmisTest.java that handles the common behavior: checking the health status of the test server, configuration settings, getting the general properties, etc.
|
||
|
||
Please take a look at [CmisDemoTests.java](src/test/java/org/alfresco/cmis/CmisDemoTests.java) class for an example.
|
||
|
||
Common configuration settings required for this project are stored in properties file, see [default.properties](src/test/resources/default.properties).
|
||
Please analyze and update it accordingly with Alfresco test server IP, port, credentials, etc.
|
||
|
||
Example:
|
||
```java
|
||
# Alfresco HTTP Server Settings
|
||
alfresco.scheme=http
|
||
alfresco.server=<add-here-the-ip-of-your-test-server>
|
||
alfresco.port=<default-port-for-alfresco-not-share>
|
||
```
|
||
|
||
* optional update the logging level in [log4j](src/test/resources/log4j.properties) file (you can increase/decrease the deails of the [logging file](https://logging.apache.org/log4j/1.2/manual.html), setting the ```log4j.rootLogger=DEBUG``` if you want.)
|
||
* go to [running](#how-to-run-tests) section for more information on how to run this tests.
|
||
|
||
**[Back to Top ^](#table-of-contents)**
|
||
|
||
### How to write a test
|
||
|
||
* Tests are organized in java classes and located on src/test/java as per maven layout.
|
||
* One test class should contain the tests that cover one functionality as we want to have a clear separation of test scope: tests for sanity/core/full, tests that verify manage of folder/files etc.
|
||
* These are the conventions that need to follow when you write a test:
|
||
* The test class has @Test annotation with the group defined: protocols, cmis. You can add more groups like sanity, regression
|
||
|
||
```java
|
||
@Test(groups={ "sanity"}
|
||
```
|
||
|
||
* The test has @TestRail annotation in order to assure that the details and results will be submitted on TestRail. The fields for TestRail annotation will be explained on next chapter.
|
||
|
||
|
||
```java
|
||
@TestRail(section = { "cmis-api" }, executionType=ExecutionType.SANITY,
|
||
description = "Verify admin user creates folder in DocumentLibrary with CMIS")
|
||
public void adminShouldCreateFolderInSite() throws Exception
|
||
{ cmisApi.usingSite(testSite).createFolder(testFolder).assertExistsInRepo(); }
|
||
|
||
```
|
||
|
||
* Use Spring capabilities to initialize the objects(Models, Wrappers) with @Autowired
|
||
* We followed Builder pattern to develop specific DSL for simple and clear usage of protocol client in test:
|
||
|
||
```java
|
||
cmisApi.usingSite(testSite) .createFolder(testFolder) .assertExistsInRepo();
|
||
```
|
||
* To view a simple class that is using this utility, just browse on [CmisDemoTests.java](src/test/java/org/alfresco/cmis/CmisDemoTests.java)
|
||
Notice the class definition and inheritance value:
|
||
|
||
```java
|
||
public class CmisDemoTests extends CmisTest
|
||
```
|
||
|
||
* as a convention, before running your test, check if the test environment is reachable and your alfresco test server is online.
|
||
(this will stop the test if the server defined in your property file is not healthy - method available in parent class)
|
||
|
||
```java
|
||
@BeforeClass(alwaysRun = true)
|
||
public void setupCmisTest() throws Exception {
|
||
serverHealth.assertServerIsOnline();
|
||
}
|
||
```
|
||
* the test name are self explanatory:
|
||
|
||
```java
|
||
@TestRail(section = { "cmis-api" }, executionType=ExecutionType.SANITY, description = "Verify admin user creates folder in DocumentLibrary with CMIS")
|
||
public void adminShouldCreateFolderInSite() throws Exception
|
||
{
|
||
cmisApi.usingSite(testSite)
|
||
.createFolder(testFolder)
|
||
.assertExistsInRepo();
|
||
}
|
||
```
|
||
|
||
```java
|
||
@TestRail(section = { "cmis-api" }, executionType=ExecutionType.SANITY, description = "Verify admin user creates and renames folder in DocumentLibrary with CMIS")
|
||
public void adminShouldRenameFolderInSite() throws Exception
|
||
{
|
||
cmisApi.usingSite(testSite).createFolder(testFolder)
|
||
.and().rename("renamed")
|
||
.assertExistsInRepo();
|
||
}
|
||
```
|
||
|
||
**[Back to Top ^](#table-of-contents)**
|
||
|
||
### How to run tests
|
||
|
||
#### from IDE
|
||
|
||
* The project can be imported into a development environment tool (Eclipse or IntelliJ). You have the possibility to execute tests or suite of tests using [TestNG plugin](http://testng.org/doc/eclipse.html) previously installed in IDE.
|
||
From Eclipse, just right click on the testNG class (something similar to [CmisDemoTests.java](src/test/java/org/alfresco/cmis/CmisDemoTests.java)), select Run As - TestNG Test
|
||
You should see your test passed.
|
||
|
||
* In case you are using the default settings that points to localhost (127.0.0.1) and you don't have Alfresco installed on your machine, you will see one exception thrown (as expected):
|
||
```java
|
||
org.alfresco.utility.exception.ServerUnreachableException: Server {127.0.0.1} is unreachable.
|
||
```
|
||
|
||
#### from command line
|
||
|
||
* In terminal or CMD, navigate (with CD) to root folder of your project (you can use the sample project):
|
||
|
||
|
||
|
||
The tests can be executed on command line/terminal using Maven command
|
||
|
||
```bash
|
||
mvn test
|
||
```
|
||
|
||
This command with trigger the tests specified in the default testNG suite from POM file: <suiteXmlFile>src/main/resources/shared-resources/cmis-suites.xml</suiteXmlFile>
|
||
|
||
You can use -Dtest parameter to run the test/suites through command line (http://maven.apache.org/surefire/maven-surefire-plugin/examples/single-test.html).
|
||
|
||
You can also specify a different suiteXMLFile like:
|
||
|
||
```bash
|
||
mvn test -DsuiteXmlFile=src/resources/your-custom-suite.xml
|
||
```
|
||
|
||
Or even a single test:
|
||
|
||
```bash
|
||
mvn test -Dtest=org.alfresco.cmis.CmisDemoTests
|
||
```
|
||
But pay attention that you will not have enabled all the [listeners](#listeners) in this case (the Reporting listener or TestRail integration one)
|
||
|
||
### Perform CMIS Queries
|
||
(:glowing_star: please notice that at this point we assert only the results count returned by the query: we plan to extend the functionality to assert on QueryResult iterable objects also: simple modification on [QueryExecutor.java](src/main/java/org/alfresco/cmis/dsl/QueryExecutor.java)
|
||
|
||
There are a couple of ways to test the results count after performing CMIS queries, choose the one that you like the most:
|
||
|
||
a) direct queries using a simple TestNG test:
|
||
|
||
(see example [here](src/test/java/org/alfresco/cmis/search/SorlSearchSimpleQueryTests.java))
|
||
```java
|
||
public class SorlSearchSimpleQueryTests extends CmisTest
|
||
{
|
||
@Test
|
||
public void simpleQueryOnFolderDesc() throws Exception
|
||
{
|
||
// create here multiple folder as data preparation
|
||
cmisApi.authenticateUser(dataUser.getAdminUser())
|
||
.withQuery("SELECT * FROM cmis:folder ORDER BY cmis:createdBy DESC").assertResultsCount().isLowerThan(101);
|
||
}
|
||
}
|
||
```
|
||
- just extend CmisTest
|
||
- authenticate with your UserModel and perform the query. The DSL will allow you to assert the result count if is equal, lower or greater than to a particular value. You can update the methods in [QueryResultAssertion](src/main/java/org/alfresco/cmis/dsl/QueryExecutor.java) class.
|
||
|
||
b) define one set of test data (folders, files, etc. ) that you will search in all tests then execute all CMIS queris from one common XML file
|
||
- see test class [SolrSearchInFolderTests](src/test/java/org/alfresco/cmis/search/SolrSearchInFolderTests.java)
|
||
- see [XML test data](src/main/resources/shared-resources/testdata/search-in-folder.xml) used in [SolrSearchInFolderTests](src/test/java/org/alfresco/cmis/search/SolrSearchInFolderTests.java) into one DataProvider. Notice that XML file has two parameter: the query that will be executed and the expected result count returned.
|
||
|
||
c) define test data (user, sites, folder, files, aspects, comments, custom models, etc) all into one XML file with all cmis queries related.
|
||
- see example on [SolrSearchByIdTests](https://gitlab.alfresco.com/tas/alfresco-tas-cmis-test/blob/master/src/test/java/org/alfresco/cmis/search/SolrSearchByIdTests.java)
|
||
- notice the 'NODE_REF[x]'; 'NODE_REF[y]' keywords that will dynamically take the test data identified by id: x, y (you will figure it out based on examples).
|
||
|
||
**Info**: all search test queries are found [org.alfresco.cmis.search](src/test/java/org/alfresco/cmis/search) package.
|
||
|
||
**[Back to Top ^](#table-of-contents)**
|
||
|
||
## Listeners
|
||
|
||
With the help of Listeners we can modify the behaviour of TestNG framework. There are a lot of testNG listener interfaces that we can override in order to provide new functionalities.
|
||
The tas framework provides out of the box a couple of listeners that you could use. These could be enabled and added at the class level or suite level.
|
||
|
||
### a) org.alfresco.utility.report.ReportListenerAdapter
|
||
|
||
* if added at the class level:
|
||
|
||
```java
|
||
@Listeners(value=ReportListenerAdapter.class)
|
||
public class MyTestClass extends CmisTest
|
||
{
|
||
(...)
|
||
}
|
||
```
|
||
|
||
* or suite xml level
|
||
|
||
```java
|
||
<suite name="Your Suite test" parallel="classes">
|
||
<listeners>
|
||
<listener class-name="org.alfresco.utility.report.ReportListenerAdapter"></listener>
|
||
</listeners>
|
||
(...)
|
||
</suite>
|
||
```
|
||
It will automatically generate one html named "report.html" in ./target/report folder.
|
||
Please also take a look at [Test Results](#test-results) section.
|
||
|
||
### b) org.alfresco.utility.testrail.TestRailExecutorListener
|
||
It will automatically update Test Rail application with the test cases that you've automated.
|
||
Please take a look at [Test Rail Integration](#test-rail-integration) section for more details.
|
||
|
||
### c) org.alfresco.utility.report.log.LogsListener
|
||
This is a new listener that will generate further details in one XML format of the automated test steps that you will write.
|
||
|
||
Example:
|
||
|
||
```java
|
||
public void myDSLMethod1()
|
||
{
|
||
STEP("Lorem ipsum dolor sit amet");
|
||
//code for first step
|
||
|
||
STEP("consectetur adipiscing elit");
|
||
//code for the next description
|
||
}
|
||
|
||
public void myDSLMethod2()
|
||
{
|
||
STEP("sed do eiusmod tempor incididunt ut labore");
|
||
//code for first step
|
||
|
||
STEP("et dolore magna aliqua");
|
||
//code for the next description
|
||
}
|
||
```
|
||
|
||
If these methods will be executed insite a test method, all those steps will be automatically logged in the XML report generated.
|
||
Example:
|
||
|
||
```java
|
||
@Test
|
||
public void adminShouldCreateFileInSite()
|
||
{
|
||
myDSLMethod1();
|
||
myDSLMethod2()
|
||
}
|
||
```
|
||
|
||
So if "testingSomething" will be executed this is what you will see on the XML file generated. (please take a look at [Test Results](#test-results) section for defining the defaul location)
|
||
|
||
Here is one example of XML file generated with these steps:
|
||
|
||
|
||
|
||
**[Back to Top ^](#table-of-contents)**
|
||
|
||
## Test Results
|
||
We already executed a couple of tests using command line as indicated above. Sweet! Please take a look at [sanity-cmis.xml](src/test/resources/sanity-cmis.xml) one more time.
|
||
You will see there that we have one listener added:
|
||
|
||
```java
|
||
<listener class-name="org.alfresco.utility.report.ReportListenerAdapter"></listener>
|
||
```
|
||
This will tell our framework, after we run all tests, to generate one HTML report file with graphs and metrics.
|
||
|
||
Take a look at the target/reports folder (created after running the tests) and open the report.html file.
|
||
|
||
|
||
|
||
Playing with this report, you will notice that you will be able to:
|
||
* search tests cases by name
|
||
* filter test cases by errors, labels, groups, test types, date when it was executed, protocol used, etc.
|
||
* view overall pass/fail metrics of current test suite, history of tests execution, etc.
|
||
|
||
The report path can be configured in default.properties):
|
||
|
||
```
|
||
# The location of the reports path
|
||
reports.path=your-new-location-of-reports
|
||
```
|
||
|
||
**[Back to Top ^](#table-of-contents)**
|
||
|
||
## Test Rail Integration
|
||
|
||
Alfresco is using now https://alfresco.testrail.net (v5.3.0.3601).
|
||
|
||
We aim to accelerate the delivery of automated test by minimizing the interaction with the test management tool - TestRail. In this scope we developed the following capabilities:
|
||
* creating automatically the manual tests in TestRail
|
||
* submitting the test results (with stack trace) after each execution into TestRail Test Runs
|
||
* adding the test steps for each test.
|
||
|
||
### Configuration
|
||
In order to use Test Rail Integration you will need to add a couple of information in [default.properties](src/test/resources/default.properties) file:
|
||
(the document is pretty self explanatory)
|
||
|
||
```java
|
||
# Example of configuration:
|
||
# ------------------------------------------------------
|
||
# testManagement.endPoint=https://alfresco.testrail.com/
|
||
# testManagement.username=<yourusername-that-you-connect-to-testrail>
|
||
# testManagement.apiKey=<api-key>
|
||
# testManagement.project=<id-of-your-project
|
||
# testManagement.testRun=<test-run-name>
|
||
```
|
||
!This settings are already defined in default.properties for you.
|
||
|
||
|
||
For generating a new API Key take a look at the official documentation, TestRail [APIv2](http://docs.gurock.com/testrail-api2)
|
||
* _testManagement.project= **<id-of-your-project**_ this is the ID of the project where you want to store your test cases.
|
||
If you want to use [Alfresco ONE](https://alfresco.testrail.net/index.php?/projects/overview/1) project in TestRail, open that project and notice the URL, after "/overview/**1**" link you will see the ID of the project (1 in this case)
|
||
If you want to use [TAS Project](https://alfresco.testrail.net/index.php?/projects/overview/7) you will notice the ID 7, so _"testManagement.project=7"_
|
||
* "_testManagement.testRun=<test-run-name>_" this represents the name of the Test Run from your project.
|
||
* In Test Rail, navigating to Test Runs & Results, create a new Test Run and include all/particular test cases. If this test run name is "Automation", update _testManagement.testRun= **Automation**_.
|
||
All test results will be updated only on this test run at runtime as each test is executed by TAS framework.
|
||
|
||
### How to enable Test Rail Integration?
|
||
|
||
We wanted to simplify the Test Rail integration, so we used listeners in order to enable/disable the integration of Test Rail.
|
||
* first configure your default.properties as indicated above
|
||
|
||
* now on your TestNG test, add the @TestRail annotation, so let's say you will have this test:
|
||
|
||
```java
|
||
@Test(groups="sample-tests")
|
||
public void thisAutomatedTestWillBePublishedInTestRail()
|
||
{
|
||
}
|
||
```
|
||
add now @TestRail integration with mandatory field ```section```. This means that this tests annotated, will be uploaded in TestRail:
|
||
|
||
```java
|
||
@Test(groups="sample-tests")
|
||
@TestRail(section = { "protocols", "TBD" })
|
||
public void thisAutomatedTestWillBePublishedInTestRail()
|
||
{
|
||
}
|
||
```
|
||
The section field, represents an array of strings, the hierarchy of sections that SHOULD be found on TestRail under the project you've selected in default.properties. Follow the TestRail [user-guide](http://docs.gurock.com/testrail-userguide/start) for more information regarding sections.
|
||
In our example we created in Test Rail one root section "protocols" with a child section: "TBD" (you can go further and add multiple section as you wish)
|
||
|
||
* now, lets add the listener, the TestRailExecutorListener that will handle this TC Management interaction.
|
||
This listener can be added at the class level or suite level (approach that we embrace)
|
||
Take a look at [sanity-cmis.xml](src/test/resources/sanity-cmis.xml) for further example.
|
||
|
||
```xml
|
||
<listeners>
|
||
<listener class-name="org.alfresco.utility.testrail.TestRailExecutorListener"></listener>
|
||
(...)
|
||
</listeners>
|
||
```
|
||
|
||
Right click on cmis-suites.xml file and run it, or just "mvn test" from root if this sample project.
|
||
After everything passes, go in Test Rail, open your project and navigate to "Test Cases" section. Notice that under protocols/TBD section, you will see your test case published.
|
||
|
||
If you defined also the "testManagement.testRun" correctly, you will see under Test Runs, the status of this case marked as passed.
|
||
|
||
The @TestRail annotation offers also other options like:
|
||
- "description" this is the description that will be updated in Test Rail for your test case
|
||
- "testType", the default value is set to Functional test
|
||
- "executionType", default value is set to ExecutionType.REGRESSION, but you can also use ExecutionType.SMOKE, ExecutionType.SANITY, etc
|
||
|
||
Take a look at the demo scenarios in this project for further examples.
|
||
|
||
**[Back to Top ^](#table-of-contents)**
|
||
|
||
## Reference
|
||
|
||
* For any improvements, bugs, please use Jira - [TAS](https://issues.alfresco.com/jira/browse/TAS) project.
|
||
* Setup the environment using [docker](https://gitlab.alfresco.com/tas/alfresco-docker-provisioning/blob/master/Readme.md).
|
||
* [Bamboo Test Plan](https://bamboo.alfresco.com/bamboo/browse/TAS-CMIS)
|
||
|
||
## Contributors
|
||
|
||
As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other... [more](CODE_OF_CONDUCT.md)
|
||
|
||
## Releasing
|
||
|
||
Any commit done on this project should be automatically executed by [TAS Build Plan](https://bamboo.alfresco.com/bamboo/browse/TAS-TAS)
|
||
If the build passes, then you didn't broke anything.
|
||
|
||
If you want to perform a release, open [TAS-CMIS](https://bamboo.alfresco.com/bamboo/browse/TAS-CMIS) Bamboo Build.
|
||
Run the Default stage and if it passes, then manually perform the Release stage (this will auto-increment the version in pom.xml)
|
||
|
||
## License
|
||
|
||
TBD
|