Skip to content
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.

Re-enable unit tests after Core 1.0.0 migration - Closes #1072 #1073

Merged
merged 7 commits into from
May 25, 2018

Conversation

slaweet
Copy link
Contributor

@slaweet slaweet commented May 18, 2018

What was the problem?

Some tests were skipped (see #1072)

How did I fix it?

I re-enabled them

How to test it?

Run the tests, read the tests

Review checklist

@slaweet slaweet self-assigned this May 18, 2018
@slaweet slaweet force-pushed the 1072-re-enable-unit-tests-after-1-0-0-migration branch from 67459af to e514232 Compare May 18, 2018 09:37
@slaweet slaweet requested a review from yasharAyari May 18, 2018 09:46
yasharAyari
yasharAyari previously approved these changes May 18, 2018
@slaweet slaweet changed the title Re-enable unit tests after Core 1 .0.0 migration - #1072 Re-enable unit tests after Core 1.0.0 migration - #1072 May 18, 2018
@slaweet slaweet force-pushed the 1072-re-enable-unit-tests-after-1-0-0-migration branch from ddcde18 to d9f29dd Compare May 23, 2018 11:35
Copy link
Contributor

@yasharAyari yasharAyari left a comment

Choose a reason for hiding this comment

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

good job. thanks @slaweet

@slaweet slaweet merged commit c14993b into 2.0.0 May 25, 2018
@slaweet slaweet deleted the 1072-re-enable-unit-tests-after-1-0-0-migration branch May 25, 2018 12:17
@slaweet slaweet changed the title Re-enable unit tests after Core 1.0.0 migration - #1072 Re-enable unit tests after Core 1.0.0 migration - Closes #1072 May 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants