This document provides an overview of Selenium, a suite of tools for automating web app testing, and introduces Fluentselenium, a simplified framework aimed at improving testing practices using domain-specific languages (DSLs). It emphasizes best practices for utilizing Selenium and XPath in testing, such as prioritizing test independence, clarity, and careful use of XPath. The document also outlines practical examples of web testing operations, along with guidelines for effective test creation and maintenance.

1. Les DSL et "fluent interface" pour les tests ASP.NET avec Selenium FluentSelenium

2. Content Selenium and XPATH

3. Best practices for testing

4. FluentSelenium

5. Conclusion

6. Selenium introduction Selenium is a suite of tools to automate web app testing across many platforms It is developed by ThoughtWorks and is available as an open source project It includes Selenium IDE : Firefox add-on that records clicks, typing, and other actions to make a test, witch you can play back in the browser Selenium Remote Control : Run your tests in multiple browsers and platforms. Tweak your tests in your prefered language (C#, Java, Perl, PHP, Python or Ruby) Uses XPATH as its web query language

7. Here's a web test written with selenium selenium.Open( "Forum/AllPosts.aspx" ); selenium.WaitForPageToLoad( "8000" ); selenium.Click( "newPost" ); selenium.WaitForPageToLoad( "8000" ); selenium.Type( "//*[contains(@id, 'txtAuthor')]" , "Luc" ); selenium.Type( "//*[contains(@id, 'txtSubject')]" , "Simple example of the library." ); selenium.Click( "//*[contains(@id, 'btnSavePost')]" ); selenium.WaitForPageToLoad( "8000" ); Assert .AreEqual( "Luc" , selenium.GetText( "//table[contains(@id, 'grdPosts')]//tr[2]/td[2]" ));

8. Xpath introduction XPath is a structred XML query language Example : get the node of the employee with ID 123456 Employees/Employee[@EmployeeID='123456'] < Employees > < Employee EmployeeID = &quot; 123456 &quot; > < LastName > Laporte </ LastName > < FirstName > Jacques </ FirstName > </ Employee > < Employee EmployeeID = &quot; 654321 &quot; > < LastName > Gendron </ LastName > < FirstName > Pierre </ FirstName > </ Employee > </ Employees >

9. Xpath introduction XPath is a structred XML query language Example : get the last name of the employee with ID 123456 : Employees/Employee[@EmployeeID='123456']/LastName < Employees > < Employee EmployeeID = &quot; 123456 &quot; > < LastName > Laporte </ LastName > < FirstName > Jacques </ FirstName > </ Employee > < Employee EmployeeID = &quot; 654321 &quot; > < LastName > Gendron </ LastName > < FirstName > Pierre </ FirstName > </ Employee > </ Employees >

10. Selenium and XPath on HTML Because HTML is an XML derivative, XPath can be used to locate nodes in a HTML web page Example : ask selenium to click on the Save button : selenium.Click(“//input[@id='btnSubmit']”); selenium.WaitForPageToLoad(“5000”); < html > < body > < form > < div >Hello World !</ div > < input type = &quot; submit &quot; value = &quot; Save &quot; id = &quot; btnSubmit &quot; /> </ form > </ body > </ html >

11. Complete simple web test with selenium

12. Content Selenium and XPATH Best practices for testing

13. FluentSelenium

14. Conclusion

15. Good testing practices Test coverage

16. Test independance

17. Test clarity

18. Test coverage Should we aim for 100% coverage?

19. The trade offs

20. What does this mean? Integrated tests Unit tests Test coverage

21. Best practices of test coverage Web tests are not cheap to write, maintain, or execute, don't strive for high coverage unless you need it

22. Favor coverage through testing of services and domain objects over UI testing

23. Use patterns that facilitate testing close to the UI layer such as MVC

24. Aim for coverage that gives you confidence in the quality of your deliverables

25. Test independance Keep tests independent because: They will be easier to fix

26. They will be easier to read

27. They will not be impacted by updates in other tests

28. Some things to consider... For better independance consider using easily rebuildable dependencies: Web server: Cassini

29. Database: Sqlite For etxternal dependencies that cannot be relied on to be performant or predictable consider using a fake implementation.

30. Test Clarity Tests need to be easy to read because they need to be maintained.

31. Tests are code also. Team code quality rules should also be applied to tests.

32. XPATH is dangerous, use it wisely Use ID-based queries when possible //*[@id = 'searchResultCount']

33. Avoid exessive XPATH steps When requiring further qualification in searches only add necessary qualifiers Favor //*[@id='searchResults']//li[1] Over /html/body//div[@id='searchResults']/ul/li[1]

34. XPATH queries are not clear Xpath expressions are the kind of literal who's meaning can be hard to decipher. Use constants. Favor selenium.GetText(SearchResultSummaryLocator); Over selenium.GetText( &quot;//*[@id='searchResultsSummary']&quot; );

35. Keep the test code clean Always revise the tests for clarity.

36. Hard to read tests are hard maintain

37. Tests serve as application behavior documentation

38. The importance of language in tests Who needs to understand your tests?

39. Know your target audience Developers

40. Users

41. Testers