Skip to content

Manual testing of Release 2022.12.1 Part 1 #1860

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

Closed
tyuldashev opened this issue Feb 27, 2023 · 1 comment
Closed

Manual testing of Release 2022.12.1 Part 1 #1860

tyuldashev opened this issue Feb 27, 2023 · 1 comment
Assignees
Labels
ctg-qa Issue is related to QA process lang-java Issue is related to Java support

Comments

@tyuldashev
Copy link
Collaborator

tyuldashev commented Feb 27, 2023

Possible values:

  • Project: Maven, Gradle, Intellij
  • JDK: 1.8, 11, 17
  • Framework: JUnit 4, JUnit 5, TestNG
  • Parametrization: On, Off

Suggestion:

Let's do independent validation of "JDK <-> Framework" and "JDK <-> Framework <-> Parametrization". Project type will equally distributed between testers.

JDK <-> Framework Pair:

All possible combinations of JDK and Framework are selected.
Project type is iterated independently.
Parametrization is OFF.

Scenario:

  1. Crete new project with specified project type, JDK.
  2. Remove default test dependency from Maven or Gradle configuration and refresh project structure.
  3. Copy paste org.utbot.examples.exceptions.ExceptionExamples and org.utbot.examples.controlflow.Conditions from UTBot project into source code folder.
  4. Invoke test generation for org.utbot.examples.exceptions.ExceptionExamples file with specific Framework - all test frameworks suggested to be installed.
  5. Generate tests - tests are generated without error with proper test Framework.
  6. Run tests - tests run without error.
  7. Invoke test generation again for org.utbot.examples.controlflow.Conditions, all except installed framework suggested to be installed.
  8. Generate and run tests with the same framework - tests are generated and executed without errors.
Project JDK Framework Status Comment
Gradle 1.8 JUnit 5
Maven 1.8 TestNG 7.5 added
Gradle 11 JUnit 5
Maven 11 TestNG 7.6 added
Maven 17 JUnit 5
Gradle 17 TestNG 7.6 added

JDK <-> Framework <-> Parametrization

All possible combinations of Parametrization and Framework need to be tested. But actually all cases with Parametrization OFF were tested in previous section, so we select only case Parametrization is ON.
Additionally Parametrization is possible only with JUnit5 and TestNG frameworks, so we leave only with 6 test cases:

JDK Framework Parametrization Status Comment
1.8 JUnit 4 On Not applicable
1.8 JUnit 5 On
1.8 TestNG On Not applicable
11 JUnit 4 On Not applicable
11 JUnit 5 On
11 TestNG On
17 JUnit 4 On Not applicable
17 JUnit 5 On
17 TestNG On
JDK Fuzzing/Symbolic Symbolic 100% Fuzzing 100%
1.8
11
17
Test Generation Timeout Fuzzing/Symbolic Symbolic 100% Fuzzing 100%
60
10
1
  • timeout limits only test generation, building and reading classes phases are not included.
@tyuldashev tyuldashev added the ctg-qa Issue is related to QA process label Feb 27, 2023
@tyuldashev tyuldashev self-assigned this Feb 27, 2023
@alisevych alisevych changed the title Manual checklist for 'Project-JDK-Framework-Parametrization' parameters Manual testing of Release 2023.03 Part 1 Feb 27, 2023
@alisevych alisevych added this to the 2023.03 Release milestone Feb 27, 2023
@alisevych alisevych added the lang-java Issue is related to Java support label Mar 14, 2023
@github-project-automation github-project-automation bot moved this from Todo to Done in UTBot Java Mar 21, 2023
@alisevych alisevych changed the title Manual testing of Release 2023.03 Part 1 Manual testing of Release 2022.12.1 Part 1 Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ctg-qa Issue is related to QA process lang-java Issue is related to Java support
Projects
Archived in project
Development

No branches or pull requests

2 participants