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

Replace all Lettuce specs by unittest+splinter #53

Open
rodrigomanhaes opened this issue Aug 28, 2011 · 1 comment
Open

Replace all Lettuce specs by unittest+splinter #53

rodrigomanhaes opened this issue Aug 28, 2011 · 1 comment

Comments

@rodrigomanhaes
Copy link
Member

Lettuce approach adds one more level of indirection (specs in plain-English are translated into fragmented Python steps). Since we don't have a non-technical customer/user that takes advantage from our plain-English specs, replacing them by functional specs in unittest using a high-level API as Splinter will increase both readability and simplicity of our specifications.

@bernardobarreto
Copy link
Member

is it really necessary at this point ? I think it would be much more hard work to change from lettuce than keep with it, because it's everything already done in the website, I mean, I don't think will come up something big that would be really easier test without lettuce.

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

2 participants