Skip to content

Conversation

@alisevych
Copy link

@alisevych alisevych commented Jul 4, 2023

Description

Fixes #3

Add more info if needed:

  • context/purpose for implementing changes
  • detailed description of the changes made

How to test

Automated tests

Please specify the automated tests for your code changes: you should either mention the existing tests or add the new ones.

For example:

The proposed changes are verified with tests:
utbot-fuzzing/src/test/kotlin/org/utbot/fuzzing/FuzzerSmokeTest.kt

Manual tests

If it is impossible to provide the automated tests, please reason why. Usually, it is relevant only for UI- or documentation-related PRs.
If this is your case, share the detailed manual scenarios that help to verify your changes.

Self-check list

Check off the item if the statement is true. Hint: [x] is a marked item.

Please do not delete the list or its items.

  • I've set the proper labels for my PR (at least, for category and component).
  • PR title and description are clear and intelligible.
  • I've added enough comments to my code, particularly in hard-to-understand areas.
  • The functionality I've repaired, changed or added is covered with automated tests.
  • Manual tests have been provided optionally.
  • The documentation for the functionality I've been working on is up-to-date.

@alisevych alisevych mentioned this pull request Jul 5, 2023
25 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

First bug

2 participants