This is brief overview of automated test framework for Acne project using selenium and sahi testing tools

1. Automation Testing Framework for Acne Ibuildings Selenium(PHPUnit) and Sahi

3. Automated Testing Framework

4. Selenium+SAHI framework

5. Introducing Pageness & data-driven tests

6. Continuous Integration with Jenkins for Sahi and Selenium

7. Demo

8. Q/A

10. Test::PHPUnit

11. Testing Tools:

12. -Selenium

13. -Sahi

14. CI : Jenkins, Ant

15. Future : Behat or PHPSpec

17. Long term, maintainable tests

18. Balance between regression Vs Smoke test suite

19. Selenium Grid

20. BDD approaches

21. Advance collaborative Test reporting

23. Phase2: data-driven, array, parameters, looping.

24. Phase3: Modular, libraries, Abstraction, UI maps, config files, global properties.

25. Phase4: keyword driven, ODBC functions, spreadsheets.

26. Phase5: Oops, everything is in object. CI, multiple types of test.Dev contributes in test suite and integrate with CI

28. Test Suite: tests, env,app,test group

29. Test configuration: URLs, username, passwords, machine configs

30. Test properties

31. Test Data Repository: XML, JSON, XLS, CVS

32. Parameterized Test

33. UI Mapping

34. Test Components

35. Test Scripts,

36. Test Reports, Logs

37. Benefits: Abstraction, multiple types of testing like unit, integration, load, generic test Api, test configuration, multithreading, CI

39. Performance

40. Frequently changing requirements

41. Combination of manual and automated testing

42. Selenium didn't work with dynamic locator

43. Geographically diverse team

44. Lack of effective JIRA workflows

45. Slow Xpath on IE with Selenium

47. Test readability become better due to pages

48. Sahi resolved performance and dynamic locators issue and wait.

49. Introducing QA in planning and estimation for better acceptance tests.

50. Collaborative method working among tester-developer-customers

52. Pages like registration, home, login, category, product, checkout, payment etc

53. Page-ness cause tests more readable

54. Page-ness hides details by abstraction of classes

55. Page-Example

56. SampleTest using Page Object

57. Sample Smoke Test :Selenium

58. Sample Url Check: Selenium

59. Sample Sahi Test

60. Sahi Checkout Test

62. Smoke tests run regularly give cross-browser feedback of basic functionality quickly.

63. Sanity tests gives feedback narrow regression within 5 min after deployment.

64. Overnight test suite run most of data-driven cross-browser tests.

65. Sahi tests executed much quicker than selenium tests

66. Integrated Sahi and Selenium with jenkins

67. Sahi build gives feedback within 3 minutes covering all basic functionality. We need that always green.

68. Example CI

69. Agile Testing

71. Collaborative acceptance tests allow everyone in team to add more tests

72. Automated build and CI

73. QA in planning and estimation

74. Well defined JIRA workflows which gives multiples eyes before releasing product

75. Team understand “Testing”

76. Everyone contribute in documentation.

77. Significant automation and continuous feedback

78. Living documentation on relish https://www.relishapp.com/sjagtap/acne

80. Configuration on different browsers

81. Introduction of page object model

82. CI with Jenkins for Sahi and Selenium

83. Used power of PHPUnit than selenium

84. Combination of Selenium and Sahi

85. Agile Test documentation

87. We have most of the features written in Gherkins already

88. We already have Sahi framework which support behat for launching browser.

89. Behat may not be alternative to unit and regression tests but it will streamline test process.

90. Demo

91. Any Suggestions? Q & A

92. Thank You !!