Recommend Lettuce users switch to Aloe

[danni]

Opening this as an issue because I think it warrants discussion. For some time @koterpillar and I were working on the new-parser branch of Lettuce which has finally grown into a fully-fledged fork based on Nose called Aloe.

It's more or less compatible with your existing Lettuce tests and comes with all the advantages of using Nose. It also has excellent debugging features with your features and steps appearing in the backtraces like they're files and functions.

It also integrates with Django-Nose through Aloe-Django and we have plans to add Aloe-FactoryBoy. There's a branch of Lettuce-Webdriver that works with Aloe.

So should we add a message inviting users to move to Aloe?

[danni]

• Aloe
• Aloe-Django
• Lettuce-Webdriver Aloe branch

[incognos]

Looks nice, but the docs are sparse and very difficult to follow with very few examples.

[danni]

@incognos what sort of things would you like to see? I'm keen to add more if people find it useful.

[incognos]

well, the docs on the lettuce site are pretty complete with examples and steps. You mention specific features outside of lettuce, but no examples are given. (also the lettuce-webdriver aloe branch link is broken above)

I was looking to replace lettuce because we are migrating from 1.6.8 to 1.8.x

[koterpillar]

Lettuce-Webdriver branch became Aloe Webdriver.

[ramast]

I gave Aloe a shot, opened few tickets. Here is the difference I noticed so far:

• harvest command doesn't accept "--no-server" parameter, u always have to use live server or understand how to make a custom TestCase class
• features directory must contain __init__.py or u won't be able to import any steps inside that dir.
• harvest will always create/destroy db after each feature (Scenario?), it seems there is no (documented?) equivalent to LETTUCE_USE_TEST_DATABASE = False

Aside from these, tests seems to be working ok

[elgalu]

Looks like I will take a look at Aloe as this project is no longer maintained.