Eclipse SKyBT Creation Review

Type
Creation
State
Ongoing
End Date of the Review Period

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.

Proposal

Eclipse SKyBT

Friday, August 9, 2024 - 04:51 by Christian Claus
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process) and is written to declare its intent and scope. We solicit additional participation and input from the community. Please login and add your feedback in the comments section.
Parent Project
Proposal State
Community Review
Background

The paradigms of testing are in transition due to cost pressure and technical evolutions (ALM repositories, model-based testing, AI, etc.).

Additionally, systems and functions becoming more and more complex. Designing and updating testcases for these can be done much easier with the help of specialized tools.

The widely used keyword and model-based testing automation approaches in the IT world are insufficiently established in the automotive industry - The industry must manage the technological leap. 

Implementing testcases in test automations is always very time consuming and keeping them up to date is a big challenge. It is way more efficient not to implement each testcase, but to implement the execution of keywords instead.

SKyBT, short for Smart Keyword Based Testing, helps to tackle these challenges.

Scope

Eclipse SKyBT (Smart Keyword Based Testing) offers a way to create necessary test cases using model and keyword-based test design methods.

The models and test cases can be combined with parameters and test data sets, while keyword and syntax management are embedded. Eclipse SKyBT integrates into existing toolchains with ALM tools and test automations.

Description

Eclipse SKyBT (Smart Keyword Based Testing)

The core idea of Eclipse SKyBT: Based on our experience from numerous projects, the success factor of testing lies in the test design, everything else can and should be automated as much as possible.

With Eclipse SKyBT the test designers are able to describe the system under test as a model by using a defined syntax and keywords. The model includes the definition and selection of the needed interfaces, logical relations as a state machine and description of the logical objects with keyword sentences.

Custom keywords can be defined as needed for the current project. Platform or communication definitions can be imported and then be used as keywords. The keyword and syntax management are embedded.

Form these keyword-based models of the system under test the test designer is able to generate the needed testcase using the testcase generator. 

Of course, the user is also able to write classic testcases based on the syntax and keywords.

The models and testcases can be combined with parameters and test data sets.

As most of the test departments already have a working test management, testcases can be exported to the used application lifecycle management tools. 

Coming from the ALM tool the configured test suites can be executed in the used test automation. Since the testcases are based on keywords, there is no need to implement or update the testcase. All testcases that are based on the already implemented keywords can be executed directly. 

Why Here?

Most of the projects in the Eclipse Automotive community are focusing on the development of functions or frameworks. There is also a strong need on testing these.

Eclipse SKyBT is grown from the requirements on test design for the automotive industry.

Eclipse SKyBT can be combined with other projects in the Ecplise automotive community, like OpenDUT.

Future Work

Adding more features and interfaces based on inputs from the community.

Adding example implementations for common test automation frameworks.

Project Scheduling

New releases are planned frequently at least once per quarter including release notes.

Committers
Lukas Langer
Joachim Ehbrecht
Fabrice Ravel
Initial Contribution
  • Source code
  • Documentation
  • Example testcases
  • Summary illustrations

    A commit of the first usable implementation is planned for the end of 2024.
Source Repository Type

Dear Eclipse SKyBT Project Leaders, 
I find this project proposal quite interesting, especially given its potential to advance testing processes in the automotive industry. 
Is there some other source/link where I can find more details about this project?

I have a few questions that I believe could help clarify some aspects of the project and its applicability:

  1. What specific challenges in automotive software testing does Eclipse SKyBT address that current keyword and model-based testing tools do not?
  2. Could you provide examples or use cases where Eclipse SKyBT could be effectively applied in real-world automotive software testing scenarios?
  3. I’m curious about how Eclipse SKyBT might leverage AI techniques to enhance testing processes, particularly in test case generation and maintenance. Are there any plans for incorporating AI-driven test case generation or predictive analytics?
  4. What specific ALM tools and test automation frameworks are planned for support by Eclipse SKyBT? How seamless can the integration process be with existing toolchains in an organization's infrastructure?
  5. How flexible is the keyword and syntax management in adapting to the diverse needs of automotive software testing? Will there be any specific user roles or skill sets required to effectively utilize SKyBT?

I look forward to learning more about how Eclipse SKyBT can contribute to the evolving landscape of automotive software testing. 

Eclipse SKyBT (Smart Keyword Based Testing)

The core idea of Eclipse SKyBT: Based on our experience from numerous projects, the success factor of testing lies in the test design, everything else can and should be automated as much as possible.

With Eclipse SKyBT the test designers are able to describe the system under test as a model by using a defined syntax and keywords. The model includes the definition and selection of the needed interfaces, logical relations as a state machine and description of the logical objects with keyword sentences.

Custom keywords can be defined as needed for the current project. Platform or communication definitions can be imported and then be used as keywords. The keyword and syntax management are embedded.

Form these keyword-based models of the system under test the test designer is able to generate the needed testcase using the testcase generator. 

Of course, the user is also able to write classic testcases based on the syntax and keywords.

The models and testcases can be combined with parameters and test data sets.

As most of the test departments already have a working test management, testcases can be exported to the used application lifecycle management tools. 

Coming from the ALM tool the configured test suites can be executed in the used test automation. Since the testcases are based on keywords, there is no need to implement or update the testcase. All testcases that are based on the already implemented keywords can be executed directly.