Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve testing strategies for TEAM Engine and/or test suites #318

Open
dstenger opened this issue Mar 8, 2018 · 3 comments

Comments

Projects
1 participant
@dstenger
Copy link
Contributor

commented Mar 8, 2018

No description provided.

@dstenger

This comment has been minimized.

Copy link
Contributor Author

commented Mar 20, 2018

Testing strategies for TEAM Engine and test suites

Structure of tests:

Testing of TEAM Engine

Testing of test suites

  • Unit tests
    • Can be written in Java and executed by Maven (if test suite is written in TestNG)
    • Not possible for test suites written in CTL.
      • Status: Can be implemented for each test suite individually
  • Integration tests
    • Can be written in Java and executed by Maven.
    • Possible solution for future: TEAM Engine Docker Image is pulled from Docker Hub, started by Maven and used for integration tests.
      • Status: Can be implemented for each test suite individually
  • System tests

@dstenger dstenger self-assigned this Mar 26, 2018

@dstenger

This comment has been minimized.

@dstenger

This comment has been minimized.

Copy link
Contributor Author

commented May 25, 2018

Create SoapUI system tests for TEAM Engine

SoapUI system tests were created for TEAM Engine:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.