-
Notifications
You must be signed in to change notification settings - Fork 45
Labels usage guidelines
Something isn't working. Indicates an unexpected problem or unintended behavior.
This label applies to the issues and pull requests related to org.utbot.engine
package.
Use it if your issue or fix deals with model construction (including Soot and Jimple),
memory modeling, symbolic values, wrappers, mocking, value resolving, or interaction
with the SMT solver.
Path selector issues generally should also have the "engine" label, unless the problem is specific to a ML-based path selection algorithm.
This label applies to the issues and pull requests related to org.utbot.intellij
module.
Use it if your changes in code are related to plugin UI appearance (mostly ui
package)
or close functionality: frameworks installation, sarif reports generation, etc.
This label applies to the issues and pull requests related to org.utbot.framework.codegen
package.
Use it if your issue or fix deals with generating (rendering) code of unit tests based on obtained
from symbolic engine executions. It may relate to generation on both supported languages (Java and Kotlin).
Code generator related class names are often marked with Cg
prefix or with CodeGenerator
suffix.
Indicates a need for improvements or additions to documentation.
This issue or pull request already exists. Indicates similar issues, pull requests, or discussions.
New feature or request.
Good for newcomers. Indicates a good issue for first-time contributors.
Extra attention is needed. Indicates that a maintainer wants help on an issue or pull request.
This issue / PR doesn't seem right. Indicates that an issue, pull request, or discussion is no longer relevant.
Further information is requested. Indicates that an issue, pull request, or discussion needs more information.
This will not be worked on. Indicates that work won't continue on an issue, pull request, or discussion.
- Check system requirements
- Install or update plugin
- Generate tests with default configuration
- Fine-tune test generation
- Get use of test results
(redirect to /docs in main repo)
- Contributing guide
- Developer guide
- Naming and labeling conventions
- Interprocess debugging
- Interprocess logging
- UnitTestBot overall architecture
- Android Studio support
- Assumption mechanism
- Choosing language-specific IDE
- Code generation and rendering
- Fuzzing Platform (FP) Design
- Instrumented process API: handling errors and results
- UnitTestBot JavaScript plugin setup
- Night statistics monitoring
- RD for UnitTestBot
- Sandboxing
- UnitTestBot settings
- Speculative field non-nullability assumptions
- Symbolic analysis of static initializers
- Summarization module
- Taint analysis
- UnitTestBot decomposition
- UtUtils class
- UnitTestBot Family changes