ReachOut for Project Leaders

You are a project leader?

Set-up a beta-testing campaign
 for your project!

  • Register your project
  • Arrange a training session
  • Promote the campaign
  • Learn from feedback

Improve your software
Align with market expectations

ReachOut for Developers

You are a developer?

Check out Existing Campaigns

Participate in research project
 beta-testing campaigns!

  • Choose your beta testing job
  • Execute the tutorial
  • Answer feed-back questions
  • Pick-up your reward

Look inside state-of-the-art software
Enhance your professional network


Check out these campaigns

STAMP_Logo_RGB_small.svg

STAMP

Software Testing AMPlification for the DevOps Team

▼ campaigns

STAMP stands for Software Testing AMPlification. Leveraging advanced research in automatic test generation, STAMP aims at pushing automation in DevOps one step further through innovative methods of test amplification. 

STAMP reuses existing assets (test cases, API descriptions, dependency models), in order to generate more test cases and test configurations each time the application is updated. Acting at all steps of development cycle, STAMP techniques aim at reducing the number and cost of regression bugs at unit level, configuration level and production stage.

STAMP raises confidence and foster adoption of DevOps by the European IT industry. The project gathers four academic partners with strong software testing expertise, five software companies (in: e-Health, Content Management, Smart Cities and Public Administration), and an open source consortium. This industry-near research addresses concrete, business-oriented objectives.

Try the STAMP toolset

Ends on:

31/12/2019

Estimated Test Duration:

2 hours

Campaign objectives

Trying the open source toolset is a free initiative that will amplify your testing efforts automatically. Experiment DSpot, Descartes, CAMP or Botsing now.

Requirements for this campaign

Download and try DSpot or Descartes or CAMP or Botsing.

Beta test instructions and scenario

Feedback questionnaire

When you are done with the testing, please fill in the feedback questionnaire.
Please note that filling in the questionnaire will be your ticket for incentives.

Incentives

You'll have nothing to lose and everything to win, including time and quality in your software releases!
Moreover, you'll be among the first to experiment the most advanced Java software testing tools.

And, as a recognition for your efforts and useful feedback, you will receive a limited edition “STAMP Software Test Pilot” gift and be added as a STAMP contributor. This offer is limited to the beta testers interacting with the team, by 30 October 2019. You will be contacted individually for a customized gift and for contribution opportunities. Please, provide a valid contact email.

Please provide your e-mail address below and in the feedback questionnaire, in order to enter the ReachOut incentives programme and so that the Campaign Manager can join you about next interactions. Find out more about Reachout informed consent.

▲ back

Reachout_web.svg

ReachOut

Beta-testing campaigns for research projects

▼ campaigns

ReachOut is a Coordination and Support Action (CSA) helping H2020 projects in the area of software technologies to implement beta-testing campaigns. ReachOut act as an operational intermediary between research projects and the open market. ReachOut helps research projects implement beta testing best practices and recruit beta-testers by running promotion initiatives. ReachOut helps develop connections between research projects and potential users and beta-testers.

Testing the ReachOut platform

Ends on:

30/06/2020

Estimated Test Duration:

30 minutes to 1 hour

Campaign objectives

The goal of this campaign is to test the ReachOut platform.
It targets H2020 projects who would like to setup a beta-testing campaign.
You can find out more about ReachOut and the methodology on this page

Requirements for this campaign

In order to start testing the ReachOut platform, you need to have ready:

  • the name, short and long description of your project
  • a logo file for your project
  • the objectives of the beta-testing campaign
  • the estimated duration it will take a beta tester to test your beta-version
  • a beta version of your software available to download
  • requirements for beta testers to test your software (list of pre-installed software, hardware requirements, operating systems constraints, ...)
  • a comprehensive test scenario and instructions
  • (optional) incentives for beta testers to participate in the campaign

Beta test instructions and scenario

In order to test the ReachOut platform, you will need to:

  1. Visit https://reachout-project.eu
  2. Register as a campaign manager
    You will need to provide your details, e-mail address, login and password.
    You will receive a message to your e-mail address with an activation link.
  3. Create your project
    You will have to fill in the project details.
  4. Create your campaign with the appropriate campaign details.
    Note that you can use the XWiki syntax for formatting the details (links, bullets, ...)
  5. Customize the questionnaire in LimeSurvey
    You can do this by clicking on the "Customize and activate the associated questionnaire" button. Log into LimeSurvey using your ReachOut login and password provided during the registration.
    Once in LimeSurvey, you can edit the questions.
  6. Activate the questionnaire in LimeSurvey
  7. Manage the progress of your campaign using the campaign dashboard
    To do this, go back to your home page on the ReachOut website, and click on the Dashboard button below your campaign details. Then, edit the dashboard, save.
  8. Fill in the questionnaire (as a beta tester)
    To do this, log out of LimeSurvey and ReachOut, go to the ReachOut website, click on "Checkout existing campaigns" and fill in the questionnaire.
  9. View the answers on LimeSurvey
    Log into LimeSurvey and go to your campaign on LimeSurvey.
    Then, click on Statistics in the left menu, then on the "Simple mode" button top left. You can view statistics about the answers that have been provided by beta testers.

Feedback questionnaire

When you are done with the testing, please fill in the feedback questionnaire.
Please note that filling in the questionnaire will be your ticket for incentives.

Incentives

By participating in this survey, you will help the ReachOut project provide a better service to research projects.

Please provide your e-mail address below and in the feedback questionnaire, in order to enter the ReachOut incentives programme and so that the Campaign Manager can join you about next interactions. Find out more about Reachout informed consent.

▲ back

decide-logo.jpg

DECIDE

Multicloud Applications Towards the Digital Single Market

▼ campaigns

DECIDE is a new generation of multi-cloud service-based software framework, providing mechanisms to design, develop, and dynamically deploy multi-cloud aware applications in an ecosystem of reliable, interoperable, and legal compliant cloud services.
DECIDE is composed of a set of tools that cover the entire DevOps pipeline, from design and development to deployment and operations. All the tools are integrated via the DevOps framework UI that provides a unified user interface and orchestrates their execution when necessary.
The main tools that are part of the DECIDE framework are:
• NFR Editor: Allows the definition of the application properties and non-functional requirements
• ARCHITECT: Provides a collection of architectural patterns and gives suggestions on the most appropriate patterns based on the defined NRFs
• OPTIMUS: Simulates and determines the best deployment scenarios based on the application properties and NFRs
• MCSLA Editor: Allows the definition of Multi Cloud Service Level Agreements.
• ACSmI: Enables the automatic discovery, contracting and monitoring of Cloud Service Provider (CSP) services for deployment of the application
• ADAPT: Handles the provisioning of CSP resources, the application deployment, configuration management and the automatic (or semi-automatic) redeployment when needed.

DECIDE Platform

Ends on:

01/03/2020

Estimated Test Duration:

3 hours

Campaign objectives

By becoming a beta tester of DECIDE you will be able to experience the full DevOps lifecycle of a multi-cloud application via the unified DECIDE DevOps framework UI.
Requirements for this campaign
• Intermediate knowledge on Cloud Computing.  
• Advanced knowledge on DevOps.

Requirements for this campaign

• Intermediate knowledge on Cloud Computing.  
• Advanced knowledge on DevOps.

Beta test instructions and scenario

Install and configure the individual services (check the “Delivery and Usage” sections on each document)
ARCHITECT cloud patterns service
OPTIMUS simulation service
MCSLA service
ACSmI discovery/contracting/monitoring services
ADAPT deployment orchestrator
ADAPT Violation handler
Install and configure DECIDE DevOps framework (check the “Delivery and Usage” section)
DECIDE DevOps framework
Connect to the DevOps framework web interface and follow the workflow to create, deploy and manage a multi-cloud application (check the “User Manual” sections on the aforementioned documents)

Feedback questionnaire

When you are done with the testing, please fill in the feedback questionnaire.
Please note that filling in the questionnaire will be your ticket for incentives.

Incentives

ReachOut goodies (ask for it!)

Please provide your e-mail address below and in the feedback questionnaire, in order to enter the ReachOut incentives programme and so that the Campaign Manager can join you about next interactions. Find out more about Reachout informed consent.

Please provide your e-mail address below and in the feedback questionnaire, in order to enter the ReachOut incentives programme and so that the Campaign Manager can join you about next interactions. Find out more about Reachout informed consent.

▲ back

cropped-melodic-logo-1.png

MELODIC

Open source multicloud management platform with allows for optimization and automation of the deployment to the different Cloud Providers (AWS, Azure, GCP, Open Stack based).

▼ campaigns

MELODIC is cloud agnostic and optimized way to multicloud. It is multi-cloud management platform created within H2020 project with the same name. The MELODIC platform will enable and optimize data-intensive applications to run within defined security, cost, and performance boundaries seamlessly on geographically distributed and federated cloud infrastructures. Applications are modelled and deployed in cloud-agnostic manner. Optimization is done continuously using Reinforcement Learning algorithms. MELODIC is fully open-source, licensed under MPL.

MELODIC - multicloud management platform

Ends on:

31/12/2019

Estimated Test Duration:

16 hours

Campaign objectives

By becoming a beta tester of Melodic you will be able to learn how to use model@runtime with automatic adaptation and optimization of deployment to multicloud. Melodic is an open source multicloud management platform which allows for optimization and automation of the deployment to the different Cloud Providers (AWS and Open Stack based).

Requirements for this campaign

  • Basic knowledge about Cloud Computing. 
  • Access to at least one Cloud Provider.

Beta test instructions and scenario

  1. Install Melodic on your machine as described on the Melodic download page (scenario1)
  2. Deploy simple two component application. scenario2.pdf
  3. Install the Eclipse oxygen-based Camel editor, which enable you to create your model, manual available on Melodic's website (scenario3)
  4. Model and deploy your own application using Melodic platform. scenario4.pdf

Feedback questionnaire

When you are done with the testing, please fill in the feedback questionnaire.
Please note that filling in the questionnaire will be your ticket for incentives.

Incentives

Melodic badge and certificate. For the first or most active beta testers, we will provide project goodies (mugs, ...).

Please provide your e-mail address below and in the feedback questionnaire, in order to enter the ReachOut incentives programme and so that the Campaign Manager can join you about next interactions. Find out more about Reachout informed consent.

▲ back

elastest.png

Elastest

ElasTest Platform is being developed within a public founded project called ElasTest: an elastic platform for testing complex distributed large software systems.

▼ campaigns

ElasTest Platform is being developed within a public founded project called "ElasTest: an elastic platform for testing complex distributed large software systems". Elastest started on January 1, 2017 and will finish on December 31, 2019.

Try ElasTest Platform

Ends on:

31/12/2019

Estimated Test Duration:

4 hours

Campaign objectives

In this campaign, you will discover a testing scenario using ElasTest. A test being executed in ElasTest can make direct use of multiple integrated services (such as Web Browsers), and the tester can see all that monitoring information in the same graphical user interface and with advanced analysis features.

Requirements for this campaign

ElasTest can run in differents platforms like Laptop, Linux VM and Server. For more information about the requirements to launch ElasTest, please visit: https://elastest.io/docs/tutorials/getting-started/

Beta test instructions and scenario

The detailed instructions to execute the beta test are available at: https://elastest.io/docs/try-elastest/

Feedback questionnaire

When you are done with the testing, please fill in the feedback questionnaire.
Please note that filling in the questionnaire will be your ticket for incentives.

Incentives

Please provide your e-mail address below and in the feedback questionnaire, in order to enter the ReachOut incentives programme and so that the Campaign Manager can join you about next interactions. Find out more about Reachout informed consent.

▲ back

The Beta-Testing Campaign Platform for Research Projects.

What is ReachOut main objective? ReachOut helps H2020 projects in the area of software technologies to develop beta-testing campaigns for their software. ReachOut helps build bridges between projects and their markets. ReachOut provides projects with end-to-end support to develop and launch beta-testing campaigns so as to enable them to concretely engage with their potential users and develop their ecosystems. Check out a recent webinar for more information. 


whatisit.svg

What is Beta-Testing?

Beta testing is intended to collect feedback from customers on a pre-release product to improve its quality. This is the last stage before shipping a product. Not only it helps finalize a product, it is also a marketing tactic that helps develop a base of early adopters. 

news.svg

News and Events


Jan16

ReachOut Webinar
more...

Dec10

POSS 2019, December 10-11, Paris
more...

Nov27

PROFES 2019 Conference in Barcelona
more...


community_icon.svg

Community

Be part of the growing ReachOut community. Subscribe to our mailing list and stay updated.

envelope_icon.svg

Contact Us

Do not hesitate to write to us directly for any other questions, proposals or partnership enquiries.



Join the community

The ReachOut platform relies on an open community of European-funded research projects, R&D engineers, early users and open source contributors. You are welcome to join the ReachOut community, share best practices for successful beta-testing campaigns and contribute to the platform's improvement. 

Site maintained by OW2