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

Test interface FS #93

Closed
mjtrangoni opened this issue Jun 9, 2017 · 4 comments
Closed

Test interface FS #93

mjtrangoni opened this issue Jun 9, 2017 · 4 comments

Comments

@mjtrangoni
Copy link
Contributor

I just wanted to point this example out, and I think It would be worth to implement for testing.
procfs has a testing interface FS.

FS represents the pseudo-filesystem proc, which provides an interface to
// kernel data structures.

You can define if you what the kernel data structure file, or just local file for testing purpose.
They use a directory called 'fixture' for those files.

The main advantage here, is that you do not have to embedded it all in code, and you can also define many cases of them for more testing possibilities. If you want to develop or fix anything at home, without a Lustre file-system you can do it too.

My 2 cents.

@mjtrangoni
Copy link
Contributor Author

I found this at weekend and I think it could be a good usecase here.

@roclark
Copy link
Contributor

roclark commented Jul 10, 2017

I created #102 which runs every metric through the entire code-chain. I had some inspiration from the node_exporter with my design but took it a step further to verify the code is actually being executed and compared on each test-run as opposed to just comparing results with a text file. Feel free to take a look and let me know if you feel this new method is sufficient.

@roclark
Copy link
Contributor

roclark commented Jul 12, 2017

@mjtrangoni is the merging of #102 sufficient to close this out?

@mjtrangoni
Copy link
Contributor Author

@roclark I agree you can close this issue. Nice work! I will be taking a close look at weekend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants