Skip to content

Add symbolic executions with force mocks in parameterized tests mode #1231

Closed
@alisevych

Description

@alisevych

Description

If symbolic executions require force mocking they can't be added to the resulting test class as parametrized tests.
Currently they are just skipped. So the test class generated in parameterized mode do not include all the test cases generated without parameterization.

It is suggested to add symbolic executions with force mocks as standard tests.
Just as has been done for Fuzzer executions in #1137

Expected behavior

The solution is to do the following in parameterized mode:

  • create parameterized tests for symbolic executions without force mocks
  • create standard tests for symbolic executions with force mocks

Potential alternatives

The solution is not ideal. There is the mix of parametrized and standard tests in one class.
The alternative - as it is working now - is to skip tests that require force mocking.

Context

Discussed with @EgorkaKulikov and @sofurihafe

Metadata

Metadata

Labels

comp-codegenIssue is related to code generatorctg-enhancementNew feature, improvement or change request

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions