GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Added pre-condition for non-empty paths in the ExecutionMetric to avoid unclear NPE #267 by amandelpie · Pull Request #567 · UnitTestBot/UTBotJava

Conversation

@amandelpie

@amandelpie amandelpie commented Jul 21, 2022 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Collaborator

Description

The ExecutionMetric works with the non-empty paths, but could obtain it sometimes.
I've added pre-condition checks and throw a few exceptions to handle it later and with the correct message.

Fixes #267

Type of Change

  • Minor bug fix (non-breaking small changes)

How Has This Been Tested?

Automated Testing

Added a new test to reproduce the condition with empty paths
ExecutionMetricTest.computeWithTwoEmptySteps

Checklist (remove irrelevant options):

  • The change followed the style guidelines of the UTBot project
  • Self-review of the code is passed
  • The change contains enough commentaries, particularly in hard-to-understand areas
  • New documentation is provided or existed one is altered
  • No new warnings
  • New tests have been added
  • All tests pass locally with my changes

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@amandelpie
Handled the bad case with the empty paths
0779b2e
@amandelpie
amandelpie requested a review from onewhl July 21, 2022 12:13
@amandelpie amandelpie changed the title Added required pre-condition for the ExecutionMetric to avoid low-level exception #267 Added required pre-condition for the ExecutionMetric to avoid unclear NPE #267 Jul 21, 2022
@amandelpie amandelpie changed the title Added required pre-condition for the ExecutionMetric to avoid unclear NPE #267 Added pre-condition for non-empty paths in the ExecutionMetric to avoid unclear NPE #267 Jul 21, 2022
onewhl
onewhl approved these changes Jul 21, 2022
View reviewed changes
@amandelpie
amandelpie merged commit c28c4f0 into main Jul 21, 2022
@amandelpie
amandelpie deleted the amandelpie/feature_267 branch July 21, 2022 14:24
@amandelpie amandelpie mentioned this pull request Jul 25, 2022
"Array is empty" error message from ExecutionDistance class in utbot-summary module #267
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@onewhl onewhl onewhl approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

UTBot Java
Archived in project

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

"Array is empty" error message from ExecutionDistance class in utbot-summary module

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@amandelpie @onewhl
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.