Why this tool?
To get a portable, maintainable and scalable solution

How ReleaseBox matches this goal?
Unique frontal interface to support every actions for software versioning and package management
Overlay on versioning solutions (SVN, CVS, …)
Native management of the webMethods and Informatica components
Automatic deliverable generation (e.g. webMethods, …)
Modular conception facilitating new interface developments (versioning solution, components, …)

What is the gain ?
Coverage increasing: of the assets required to ensure the versioning and the packaging of the software delivery
Tasks simplification: simplify, with its single interface, the manipulation of complex versioning and packaging mechanisms
Secure deliverables generation: improving the delivery package consistency

Why this tool?
Ensure consistency of the code and the quality of deliverable 

How AnalyzeBox matches this goal?
Looking for unsafe source code that can generate incident at run-time
Detection of prohibited use of services or features at deliverables (eg. backup or restoration of webMethods Pipeline, ...)
Identification of « dead » source code
Preventing service locks
Checking of basic naming rules that ensure the comprehension of the and facilitate the maintenance. 

What is the gain?
Reducing the risks of bugs: controlling in advance the code helps to reduce the risks of defect detected in the following phases of the application build project
Generating a full report: helping developers to detect and solve problems
Improving the developer's productivity: the periodic control helps the developer in the respect of rules that gives homogeneity and clarity to the source code simplifying bug fixing and evolution.

Why this tool?
To reduce at maximum manuals tasks and unavailability periods due to application deployment in critical environments 

How InstallBox matches this goal?
Full automated: the actions requested to realize a software deployment are completely automated
Secure: The rollback management enable retrieving a consistent state in case of failure during deployment process
Multi-technology: the solution targets integration software suites (editors and open-source) with an adapted requirement coverage
Modular: the architecture of the solution simplifies the adaptation of the tool to meet the regular needs of upgrade. 

What is the gain?
Decreasing documentation effort
Human errors: by minimizing manual operation, operation errors and misunderstanding are avoided
Reducing delays and unavailability to operational deployment
Improving security by including roll-back procedure

Why this tool?
To easily define automated test cases that suits the technology requirements and/or functional logic of each application 

How TestBox matches this goal?
Portability – TestBox can be set-up on all platforms
Standardization of writing test cases with the XML declarative language
Modularity - organizing within test campaigns, test case sequences according functional areas
Multi-technologies - TestBox manages native webMethods and Informatica components as well as many technologies (DBMS, JMS, email, FTP, HTTP ...)
Integrating – coupling to HP ALM is enabled using Import/Export functionalities 

What is the gain?
Simplifying the definition of test cases: by providing an intuitive language and a modular structure
Facilitating the evaluation of tests generating automatically a report of the test session through a comparison with referenced results
Scalable to technological evolutions

Why this tool?
To test applications independently with a portable solution 

How SimulateBox matches this goal?
Native management of many technologies (SGBD, Web service, mail, FTP, HTTP, …)
Simulation of a client : interactions performed by a "Customer" service partner.
Service simulation: simulates the service provided by a partner
« Proxy » mode to record dataset from real exchanges.
Automatic dataset generation from Excel document 

What is the gain?
Simplifying the injection flow in the application
Complex orchestrations simulation: allows to test high complexity applications
Improve agility of Information System : facilitating tests between applications (decreasing dependencies: availability, planning constraints, security requirements, …)
Adaptable to technological evolutions
Complementary with TestBox solution

The ability to ensure the quality of developments throughout the project life cycle is a key point to improve productivity and reduce risks during the different phases of the project. In the SOA world, the use of integration suites like webMethods or Informatica requires a dedicated answer to this topic.

In order to ensure the quality of its delivery, Atos invests in the creation of a comprehensive and efficient tool that can audit developments of webMethods or Informatica applications.
The solution integrates our analyze of the main rules to follow during development phases in order to ensure homogeneity and the quality of the applications.

Designed by our expert teams, AnalyzeBox module allows auditing the code according to rules based on the standards and best practices of integration or SOA project:

• Looking for unsafe code
  that can generate incident at run-time,
  
• Detection of prohibited use
  of services or features (i.e. backup services or restoration of webMethods pipeline),
  
• Identification of “dead” code
  affecting code clarity and delivery time,
  
• Preventing service locks
  that increases risks at delivery,
  
• Verification of basic naming rules
  that ensures the comprehension of the development and facilitates its maintenance.

Without any particular set-up effort, you can quickly get the benefits of setting up AnalyzeBox in your development environment by:

• Reducing the risk of anomalies:
  The control in advance of the code helps to reduce the risks of defect detected in the different phases of the project,
  
• Give traceability to your quality efforts
  Simplifying the developer task to solve the problems by providing a complete report of the audit process
  
• Improving developer productivity:
  the regular control helps the developer in the respect of rules that gives homogeneity and clarity to the development and simplifies the bug fixes or evolution.

Analysis can be launched from either Jenkins or a shell command. Then AnalyzeBox gets the development components from WebMethods Integration Server, analyze them according to predefined XML rules and builds a report which can be imported in Sonar. At last results can be consulted either with a simple editor or from the Sonar GUI.

Analysis can be launched either from Jenkins or a shell command. AnalyzeBox analyses the development components from the Informatica database according to predefined XML rules and builds a report which can be imported in Sonar. At last the results can be consulted either with a simple editor or from the Sonar GUI.

The rules (or measures) are described in 2 XML files : 

• A RuleSet (or MeasureSet) file which contains for each rule (or measure) its name, description, priority and links to the XPATH or SQL Requests flle. 
• A XPATH or SQL Requests file which contains for each rule (or measure) the XPATH expression or SQL request that allows to process it.

The results can be imported in and consulted from Sonar.
The violations results are classified by severities and leading indicators (upward or downward) are updated after each analysis.
Sonar shows the packages (or components) with violations and the violated rules by package (or component).

Sonar allows selecting measures to be displayed. Search criteria and measures to be displayed can be saved (logged in only).

Application testing automation is needed to ensure non-regression test execution, reduce the running cost, minimize the risk of human errors and maximize the test coverage. Encouraged by the variety of Information System contexts, the on-the-shelf solutions cannot adapt themselves to the issues raised by the various interface technologies and constraints. Homemade solutions, neither easily adaptable to changes nor expandable, are finally chosen with a low level of service. Consequently, many test cases remain performed manually.

The need to easily define automated test cases that suit the technology requirements and/or functional logic of each application has motivated Atos teams to set-up a universal, modular and scalable testing tool.

Designed by our expert teams in collaboration with acceptance test supervisors, TestBox module is designed to meet the following requirements: 

• Being available for every environment. Enabling a set-up on any platform thanks to its Java implementation. 
• Simplifying test case definition. Writing test cases is made easier with a comprehensive XML declarative language. 
• Structuring test campaigns. Organizing tests, test case sequences according functional areas. 
• Integrating several technologies. Managing native webMethods and Informatica components as well as many technologies (DBMS, JMS, email, FTP, HTTP ...) 
• Automatically generating a report on tests result. 
• Being consistent with test repository. Coupling to HP ALM is possible using import/export functionalities.

Now, our customers have a test tool that automatically validates the different releases of their applications and reduces the duration of their development cycle by: 

• Reducing development cycle. With the optimization of the duration of test campaign execution. 
• Giving readability and traceability. Thanks to an intuitive language and a modular structure for test campaign. 
• Facilitating the technology evolution. Upgrade is enabled setting-up some new technology plug-ins. 
• Sustaining your investments. Because of its compliancy it's complementary with reference market test tools like HP ALM.

TestBox offers a complete range of connectors allowing to interface with a large number of systems: 

• HTTP(S), REST service, web-service with WS-Security 
• Databases (Oracle, MySQL, SQL Server, DB2, MongoDB) 
• Java Messaging Service (ActiveMQ, webMethods Broker) 
• FTP, SFTP, SSH, Telnet 
• SOA/EAI webMethods, ETL Informatica
  
  Based on these connectors, TestBox provides a wide set of actions: 
• A hundred of directly usable actions 
• Easily expandable by the addition of “custom“ action

TestBox offers a powerful comparison engine allowing to validate the test by comparing the expected data to the resulting data.

Various native formats:

• Text: XML, properties (key/value), Text, CSV
• Binary: PDF, Excel, tar, tar.gz, zip, .z

Enhanced capabilities: 

• Dynamic computing can be applied though regular expression, configuration and dynamic parameters or predefined variables 
• Structure of data can be taken into account

TestBox automatically generates a JUnit report providing every test status (Success, Failure, Error) and the success rate as well.
TestBox allows also to : 

• Notify by e-mail the person who is in charge of the tests of the tests in error 
• Notify by e-mail the project manager of an overview of the tests run

TestBox allows interfacing with HP ALM.
In an ascending way: 

• Definition of the HP ALM tests cases from the TestBox cases 
• Valuation of tests results from the TestBox results
  
  In a descending way: 
• Execution of TestBox tests from HP ALM

TestBox allows the continuous integration process implementation on a project. 

• Integration in Jenkins through the implementation of a parameterized Job 
• Integration in SONAR through the installation of a TestBox plugin

TestBox provides an Eclipse plugin in order to be fully integrated with your current IDE: 

• Execution of the tests as well as the tests campaigns simply by a click 
• Contextual help during test design 
• Assistance through an auto-completion mechanism 
• Directly usable and customizable test patterns are provided