Switch all LevelDB stores in unit tests to memory database

[antonlerner]

Overview / Motivation

We shouldn't use any persistent parts in our unit tests

The Task

Currently, we use database.NewLevelDbStore to create the DB for meshDB in the unit tests,
We should use only MemoryDB for unit tests.
Replace all occurrences of database.NewLevelDbStore in out unit tests to MemDatabase

Time Estimation

4 hours

Implementation Notes

check out block_listener_test.go

Contribution Guidelines

Important: Issue assignment to developers will be by the order of their application and proficiency level according to the tasks complexity. We will not assign tasks to developers who have'nt introduced themselves on our Gitter dev channel

1. Introduce yourself on go-spacemesh dev chat channel - ask our team any question you may have about this task
2. Fork branch develop to your own repo and work in your repo
3. You must document all methods, enums and types with godoc comments
4. You must write go unit tests for all types and methods when submitting a component, and integration tests if you submit a feature
5. When ready for code review, submit a PR from your repo back to branch develop
6. Attach relevant issue to PR

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 0.3 ETH (36.27 USD @ $120.9/ETH) attached to it as part of the Spacemesh - https://spacemesh.io fund.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $41,132.77 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

These users each claimed they can complete the work by 10 months, 1 week from now.
Please review their action plans below:

1) alonp99 has been approved to start work.

Hey, I would like to take this one :)

Learn more on the Gitcoin Issue Details page.

2) techswappy has applied to start work (Funders only: approve worker | reject worker).

Familiar with in-memory database usage and how to migrate it. Can explore the codebase to understand the specific requirement here.

Learn more on the Gitcoin Issue Details page.

[almogdepaz]

@antonlerner an integration test should be add instead
use
if testing.Short() {
t.Skip()
}

in the start of it

[gitcoinbot]

@alonp99 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[alonp99]

@gitcoinbot working on it

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work for 0.3 ETH (34.74 USD @ $115.79/ETH) has been submitted by:

1. @alonp99

@avive please take a look at the submitted work:

• PR by @alonp99

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $51,432.24 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

The funding of 0.3 ETH (34.13 USD @ $113.78/ETH) attached to this issue has been approved & issued to @alonp99.

• Learn more on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $52,354.89 more funded OSS Work available on the Gitcoin Issue Explorer