ARMmbed / ARMmbed/mbed-drivers

The test environment needs to live somewhere else

Open
#47 6 comments 0 reactions 0 assignees View on GitHub
mirrored
Dominant language
C++
Stars
39
Forks
41
PR merge metrics
No merged PRs in 30d

Description

I'm writing https://github.com/ARMmbed/mbed-util and I'm trying to **not** make it depend on `mbed-core`. The problem is that I need to write tests for that library, so now I have to use this:

```
"testDependencies": {
"mbed-core": "~0.2.0"
}
```

in order to get the test environment in the library. This is just a very awkward hack, not a solution. It looks like the test environment should live in its own repository. Yup, another repository.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with mbed-util's testDependencies entry, which currently pulls in mbed-core, and trace how that provides the test environment. Define the separate test-environment repository boundary and verify that mbed-util can run its tests without depending on mbed-core.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
embedded-iot, testing
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.