Skip to content
This repository was archived by the owner on Feb 1, 2023. It is now read-only.

fix: isFullRescanRequested() should be False after rescan finished and before UI updates [ROAD-439] #26

Conversation

ArtsiomCh
Copy link
Contributor

fix: isFullRescanRequested() should be False after rescan finished and before UI updates;
chore: mocks skeleton for .core tests created.

…d before UI updates;

chore: mocks skeleton for .core tests created.

import java.util.Collection;

public class AnalysisDataBaseMock extends AnalysisDataBase {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe where is some reason, but why not use some mock library?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel there are too many thing to mock there as far as all that abstract classes are cross linked internally a lot.
Looks like it's easier to create "mock" versions of all needed abstract classes and run test against them
But your approach might be working too, may be I just have not enough experience with using Mockito.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ArtsiomCh I don't mind. It happens that I do so too. I think you know better 👍

Copy link

@aldanchenko aldanchenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@ArtsiomCh ArtsiomCh merged commit 75041d1 into master Oct 19, 2021
@ArtsiomCh ArtsiomCh deleted the fix/isFullRescanRequested_should_be_false_after_scan_finished branch October 19, 2021 09:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants