Selenium + Wiki = “Live Requirements”<br />Mikalai Alimenkou<br />http://xpinjection.com<br />26.02.2011<br />
Background<br />Java Technical Lead/Scrum Master at Zoral Labs<br />6+ years in software development<br />4+ years of work...
Agenda<br />Wiki for requirements<br />FitNesse<br />Selenium role<br />Existing solutions<br />Benefits<br />
What is Wiki?<br />Groupware<br />No HTML<br />Simple<br />Communication<br />Open<br />Reliable<br />Knowledge Base<br />...
How Wiki Works?<br />
Wiki is Ideal for Requirements<br />Whole team can collaborate and make changes<br />Accessible by web<br />All historical...
Wiki Success<br />
What is the Source of Tests?<br />
Where is Right Place for Selenium?<br />Delivery Pipeline<br />?<br />
Test Components<br />Application Driver<br />Test Data<br />Test<br />Logic<br />
What is the Primary Goal?<br />To enable reliable stable tests we need to separate all parts as much as possible<br />
Ideal Testing Framework<br />Test Data Storage<br />Technical Data Storage<br />
FitNesse Overview<br />Standalone Wiki server<br />No configuration or setup<br />Different programming languages support<...
FitNesse Sample<br />Ignored<br />Executed<br />
FitNesse Architecture<br />
Roles and Responsibilities<br />Customer writes text <br />document with <br />examples in tables<br />Technical staff enh...
Fitnium<br />100% FitNesse<br />Fixtures for Selenium commands<br />Selenium RC run separately<br />Tiny integration layer...
Fitnium Demo<br />
Selenesse<br />Most fresh Selenium and FitNesse integration framework<br />Doesn’t include Selenium RC in installation<br ...
Selenesse Demo<br />
StoryTestIQ<br />Mix of Selenium Core with FitNesse<br />All features of FitNesse<br />Extended test management (tagging, ...
StoryTestIQ Demo<br />
Selenium + FitNesse: Benefits<br />Tests may be created by nontechnical people<br />Tests are run directly from requiremen...
Any Questions?<br />
Upcoming SlideShare
Loading in …5
×

Selenium + Wiki = Executable Specification

11,039 views

Published on

Presentation from first Selenium conference in Europe - Selenium Camp (http://seleniumcamp.com) about using Selenium with Wiki instruments for requirements management.

Published in: Technology
0 Comments
8 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
11,039
On SlideShare
0
From Embeds
0
Number of Embeds
6,324
Actions
Shares
0
Downloads
0
Comments
0
Likes
8
Embeds 0
No embeds

No notes for slide

Selenium + Wiki = Executable Specification

  1. 1. Selenium + Wiki = “Live Requirements”<br />Mikalai Alimenkou<br />http://xpinjection.com<br />26.02.2011<br />
  2. 2. Background<br />Java Technical Lead/Scrum Master at Zoral Labs<br />6+ years in software development<br />4+ years of working by Agile methodologies<br />Expert in Agile engineering practices<br />Agile coach (TDD, Testing, Planning, etc.)at XP Injection (http://xpinjection.com)<br />
  3. 3. Agenda<br />Wiki for requirements<br />FitNesse<br />Selenium role<br />Existing solutions<br />Benefits<br />
  4. 4. What is Wiki?<br />Groupware<br />No HTML<br />Simple<br />Communication<br />Open<br />Reliable<br />Knowledge Base<br />Organic<br />Easy Access<br />
  5. 5. How Wiki Works?<br />
  6. 6. Wiki is Ideal for Requirements<br />Whole team can collaborate and make changes<br />Accessible by web<br />All historical changes are available<br />Authorized access<br />Single observable requirements knowledge base<br />No technical skills required<br />File attachments and images available<br />Event notifications<br />
  7. 7. Wiki Success<br />
  8. 8. What is the Source of Tests?<br />
  9. 9. Where is Right Place for Selenium?<br />Delivery Pipeline<br />?<br />
  10. 10. Test Components<br />Application Driver<br />Test Data<br />Test<br />Logic<br />
  11. 11. What is the Primary Goal?<br />To enable reliable stable tests we need to separate all parts as much as possible<br />
  12. 12. Ideal Testing Framework<br />Test Data Storage<br />Technical Data Storage<br />
  13. 13. FitNesse Overview<br />Standalone Wiki server<br />No configuration or setup<br />Different programming languages support<br />Software acceptance testing tool<br />Run tests inside requirements pages<br />Support RTF (Running Tested Features) metric<br />
  14. 14. FitNesse Sample<br />Ignored<br />Executed<br />
  15. 15. FitNesse Architecture<br />
  16. 16. Roles and Responsibilities<br />Customer writes text <br />document with <br />examples in tables<br />Technical staff enhance<br />tables to provide FIT data<br />Test document <br />(HTML or text)<br />with sketch <br />tables<br />Test document <br />(HTML)<br />with sanitized <br />tables<br />Feedback<br />Test document <br />(HTML) and <br />backing code<br />EXECUTABLE TEST<br />Technical staff implements<br />fixtures in programming<br />language to process <br />FIT tables<br />
  17. 17. Fitnium<br />100% FitNesse<br />Fixtures for Selenium commands<br />Selenium RC run separately<br />Tiny integration layer<br />Supported by GojkoAdzic and Jeremy D. Miller<br />
  18. 18. Fitnium Demo<br />
  19. 19. Selenesse<br />Most fresh Selenium and FitNesse integration framework<br />Doesn’t include Selenium RC in installation<br />Support main set of Selenium commands<br />Growing set of helpful utility commands<br />
  20. 20. Selenesse Demo<br />
  21. 21. StoryTestIQ<br />Mix of Selenium Core with FitNesse<br />All features of FitNesse<br />Extended test management (tagging, suites, virtual directories, refactoring)<br />IDE for writing and debugging tests<br />Reusable components support<br />Database related actions<br />Helpful documentation<br />Quick start<br />
  22. 22. StoryTestIQ Demo<br />
  23. 23. Selenium + FitNesse: Benefits<br />Tests may be created by nontechnical people<br />Tests are run directly from requirements<br />Large set of supported commands<br />FitNesse provide test management Wiki server <br />Selenium tests may be mixed with acceptance tests<br />Acceptance tests may use Selenium commands<br />Selenium RC executes all tests<br />Remote server is started and controlled separately<br />
  24. 24. Any Questions?<br />

×