Releasing a big software product frequently on the same high quality level could became an impossible task. Story Testing approach gives a possibility for many teams to work for a same product and release it without putting enormous efforts on testing. Approach is based on the BDD technique, Feature Flags and Selenium.

1. Story Testing Approach for Enterprise
Applications using Selenium
Framework
Oleksiy Rezchykov
February 2011

2. Plan
• About me
• The Problem
• Solution
• Conclusion
• Q&A

3. About me
• Oleksiy Rezchykov
• Java Software Engineer
• Team Lead
• Agile & Lean enthusiast
• Lohika Systems

4. The Problem
To release a BIG product

5. What is a BIG product?
Several platforms

6. What is a BIG product?
Multiple distributed teams

7. What is a BIG product?
• Different processes (Iterative and not)

8. What is a BIG product?
Dozens of features

9. What is a BIG product?
One codeline

10. What is a BIG product?
Releases every 2-3 weeks

11. How the features usually are released
Implemented
Tested
Bugs fixed after the test
Tested after fix
And … Regression

12. Integration with the trunk
Tested
Bugs fixed after the test
Tested after fix
And … Regression

13. The release branch is created
Tested
Bugs fixed after the test
Tested after fix
And … Regression

14. The Problem : Summary
Activity Performed (# times)
Tested 5
Bugfix 3
Regression 3

15. Solution : At low level
• Automated frontend tests using
Selenium RC
• PageObject pattern for Selenium
infrastructure
• BDD Tool (Concordion)
• TestNG

16. Solution : At low level

17. Solution : At low level

18. Solution : At low level

19. Solution : At low level

20. Solution : At low level

21. Solution : Overview
TestNG suite
Concordion Selenium RC
scenario server
PageObject Selenium
methods Driver

22. Solution : Process level
• Continuous Integration Server

23. Solution : Process level
• REST API called StoryTest Set-Up
SetUp Page REST API
PageObject
Object Resource

24. Solution : Process level
• REST API called StoryTest Set-Up

25. Solution : Overview
Selenium Selenium RC
CI job
Driver server
PageObject
Maven goal
methods
Concordion
TestNG suite
scenario

26. Solution : Process level
• Feature Flags

27. Solution : Process level
• Regression suite is formed using previous
release StoryTests

28. Solution : Process level
• No testers only QA
Developer + Tester = PD

29. Conclusion
Selenium is a powerful tool – learn to use it.

30. Conclusion
Let it be the part of your process

31. Contacts
http://ua.linkedin.com/in/arezchikov
orezchykov@lohika.com
alex.mcgray@gmail.com
arezchikov

32. Q&A
???