New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-enable unit tests disabled in Core 1.0.0 migration #1072

Closed
slaweet opened this Issue May 17, 2018 · 1 comment

Comments

1 participant
@slaweet
Member

slaweet commented May 17, 2018

Expected behaviour

Tests skipped in #1032 should be re-enabled

Actual behaviour

These tests were skipped in #1032 :

describe.skip('actions: peers', () => {

it.skip(`should action data to only have activePeer on ${actionTypes.activePeerSet} action`, () => {

describe.skip('getAccount', () => {

@slaweet slaweet created this issue from a note in Version 2.0.0 (Issues) May 17, 2018

@slaweet slaweet self-assigned this May 17, 2018

@slaweet slaweet added *medium and removed *easy labels May 18, 2018

slaweet added a commit that referenced this issue May 25, 2018

Merge pull request #1073 from LiskHQ/1072-re-enable-unit-tests-after-…
…1-0-0-migration

Re-enable unit tests after Core 1.0.0 migration - #1072
@slaweet

This comment has been minimized.

Show comment
Hide comment
@slaweet

slaweet May 25, 2018

Member

Fixed in #1073

Member

slaweet commented May 25, 2018

Fixed in #1073

@slaweet slaweet closed this May 25, 2018

Version 2.0.0 automation moved this from Issues to Closed Issues May 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment