Tapestry. It has the exact same API but a lot more clean code and is more amenable to being used with my other test solutions. I recommend looking at Tapestry rather than Symbiont as I'm hoping to continue primary work with the new gem.NOTE: Symbiont is now framed as
Symbiont provides a semantic domain-specific language that can be used to construct a fluent interface for test execution libraries. The initial focus will be on using the watir-webdriver API as the underlying driver library.
What is this?
Symbiont is a test solution micro-framework.
A micro-framework provides a focused solution, which means it does one thing and one thing only, instead of trying to solve each and every problem. While doing that one thing it does well, the micro-framework should do it while being expressive yet concise. Further, it should be able to serve as one component of your own custom modularized framework, allowing you to compose solutions. To that end, you can use Symbiont directly as an automated test library or you can use it with other tools such as RSpec, Cucumber, or my own Specify tool.
In terms of what Symbiont does, it provides a way to describe your application in terms of activity and page definitions. Those definitions can then be referenced as part of the DSL that Symbiont provides. This DSL can be utilized in the context of the Watir-WebDriver test library.
The DSL provides a fluent interface that can be used for constructing test execution logic. This fluent interface promotes the idea of compressibility of your test logic, allowing for more factoring, more reuse, and less repetition.
To get the latest stable release, add this line to your application's Gemfile:
To get the latest code:
gem 'symbiont', git: https://github.com/jeffnyman/symbiont
After doing one of the above, execute the following command:
You can also install Symbiont just as you would any other gem:
$ gem install symbiont
You can check out the Symbiont Watir test script or the Symbiont Capybara test script for an idea of how the library can be interacted with. Do note that the test scripts will use my Decohere web application. To execute the test scripts, do one of the following:
$ rake scripts:watir $ rake scripts:capybara
Why call it Symbiont?
If you are a comic book reader, particularly in the Marvel Universe, you will know of the Klyntar, a race of symbiotic creatures. While those creatures have been a mixed bag in terms of good and evil, they are symbionts, which are organisms that exist in a partnership with something else. The terms comes from the Greek symbiōtēs ("companion"), from an earlier term symbioun ("to live together").
A "symbiont" is an organism in a symbiotic (mutually beneficial) relationship. Some of these relationships are called obligate, which means that both organisms need each other in order to survive. Other such relationships are called facultative, meaning that both organisms don't strictly need each other to survive, but they stand a better chance if they do.
Symbiotic relationships include associations in which one organism lives on another organism -- ectosymbiosis -- or where one organism lives inside the other -- endosymbiosis.
So, with that bit of context, think of this library as a facultative, endosymbiotic organism that lives within your test logic, giving it strength and sustenance.
Bug reports and pull requests are welcome on GitHub at https://github.com/jeffnyman/symbiont. The testing ecosystem of Ruby is very large and this project is intended to be a welcoming arena for collaboration on yet another testing tool. As such, contributors are very much welcome but are expected to adhere to the Contributor Covenant code of conduct.
To contribute to Symbiont:
- Fork the project.
- Create your feature branch. (
git checkout -b my-new-feature)
- Commit your changes. (
git commit -am 'new feature')
- Push the branch. (
git push origin my-new-feature)
- Create a new pull request.
Thanks to Jeff Morgan (http://www.cheezyworld.com/) for his page-object gem, Alister Scott (http://watirmelon.com) for his watir-page-helper gem, Alex Rodionov (http://p0deje.blogspot.com/) for his watirsome gem, and Nat Ritmeyer (http://www.natritmeyer.com/) for his SitePrism gem.