Skip to content
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

Update unit tests to provide consistent directory map #460

Closed
jphickey opened this issue May 14, 2020 · 0 comments · Fixed by #461
Closed

Update unit tests to provide consistent directory map #460

jphickey opened this issue May 14, 2020 · 0 comments · Fixed by #461
Assignees
Labels
enhancement unit-test Tickets related to the OSAL unit testing (functional and/or coverage)
Milestone

Comments

@jphickey
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The "file-api-test" and "osal_loader_UT" unit tests rely on a real FS_BASED directory map that is provided by the BSP. This creates an undesired dependency on the BSP volume table in these test cases, in that they must provide a map for /cf.

Describe the solution you'd like
Test should be BSP-agnostic. A map for the directory used by the test case can be provided locally as part of this test setup. A relative system directory can be used (e.g. "./test") to make this platform-agnostic.

Additional context
This will allow to run unit tests without a BSP-provided volume table.

Requester Info
Joseph Hickey, Vantage Systems, Inc.

@jphickey jphickey self-assigned this May 14, 2020
@skliper skliper added this to the 5.1.0 milestone May 14, 2020
@astrogeco astrogeco added the unit-test Tickets related to the OSAL unit testing (functional and/or coverage) label Sep 28, 2020
jphickey pushed a commit to jphickey/osal that referenced this issue Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement unit-test Tickets related to the OSAL unit testing (functional and/or coverage)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants