8000 Create Test Suite · Issue #27 · arkOScloud/genesis · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Create Test Suite #27

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.

Sign up for GitHub

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

Jump to bottom
Open
ajvb opened this issue Apr 24, 2013 · 4 comments
Open

Create Test Suite #27

ajvb opened this issue Apr 24, 2013 · 4 comments
Labels
enhancement
Milestone
1.0

Comments

@ajvb
Copy link
ajvb commented Apr 24, 2013

This is a proposal to design and develop a test suite for Genesis. How the test suite will be designed is open for discussion, but I my suggestion is to start with core integration testing, with separate test files for each file/module. Later on there can be discussion of UI testing with Selenium.

Decisions

  1. What testing framework to use?
    • My favourite is py.test, but I have heard nose is good as well.
  2. Where to put the test suite?
    • Pretty much up to @jacook, but I suggest in genesis in a directory named "tests"
  3. What to start with, testing wise?
    • Integration testing on the API (genesis.api) and the Plugin API (genesis.plugins.core) is probably the best place to start. But quickly, everything in mentioned in the documentation should be tested.

more to be added soon.
@peakwinter
Copy link
Contributor

If you prefer py.test then I see no reason not to use that.
The directory can be genesis/tests, that's fine
If you want to get the testing framework started then feel free and I can help build on it from there as needed. Like I said I don't have much experience with it so perhaps a little shove in the right direction would be helpful :)

Thanks!

@peakwinter
Copy link
Contributor

For now I'm putting this at 1.0 but depending on how much work is required then that can be adjusted when it becomes clear.

@ajvb
Copy link
Author
ajvb commented Apr 26, 2013

If you want to get the testing framework started then feel free and I can help build on it from there as needed. Like I said I don't have much experience with it so perhaps a little shove in the right direction would be helpful :)

Sounds good. I will get started on this once I have my Raspberry Pi and have set-up a development environment of testing Genesis. @jacook: If you have any suggestions for setting up a testing environment for Genesis, please either post them here or send me an email.

For now I'm putting this at 1.0 but depending on how much work is required then that can be adjusted when it becomes clear.

Having at least the beginnings of a test suite will be important for 1.0 I believe, but we will just have to see how things good.

@peakwinter
Copy link
Contributor

Only took me three years, but a testing framework is set up in the Core library, and I started by writing some tests for LDAP integration. All that remains is to write tests for everything else ;)

@peakwinter peakwinter modified the milestones: 1.0, 0.9 Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
2 participants
@peakwinter @ajvb
0