Testing And Drupal
Download as PPT, PDF2 likes1,062 views
Testing code through automated tests is important to ensure security and catch bugs early in the development process. There are different types of tests like unit tests which test individual functions and modules, and functional tests which test overall page behavior and interactions. Writing tests requires considering what to test, test organization, and dealing with limitations of testing tools.
![Functional test sample public class SearchTest extends FunctionalTest { function testFindResult() { this.openBrowser('firefox'); this.open('http://www.example.com', 30000); this.type("//input[@id='search-field']", "Harrr"); this.click("//fieldset/input[@type=submit]"); this.waitForPageToLoad(30000); this.assertTestPresent("regexp:\\d+ results found.*"); this.assertCookieExists('MySessionID'); } }](https://image.slidesharecdn.com/testinganddrupal-090311174539-phpapp02/85/Testing-And-Drupal-8-320.jpg)
Testing And Drupal
- 1. Testing
- 2. Why we need to test our code (site)? Ensure security Check semantic and syntax In a small team you can track changes It can reveal bugs in a very early stage of development Environment validation Fast Permanent (not like us:( ) TDD - (later)
- 3. Testing types Unit Test PHPUnit (PHP) SimpleTest (PHP) jUnit (Java) NUnit (C#) ... Functional Test Selenium IDE (html) Grid (???) Remote Control Core Castle
- 4. Testing in common use Grouping test suites -> test tree Optional start node Set-Up <-> Tear-Down Every single test could be a separate workflow Arbitrary extension capability (SimpleTest -> SimpleBrowserTest) Skip tests
- 5. Testing functions check if on value is... a specific value true false not null null check if an element / object exists not exists equal to ... check if an error (exception) occure check if an event triggered
- 6. Browser element properties Locators id=___ name=___ dom=___ (javascript object) xpath=___ link=___ css=__ Matchings glob:___ refexp:___ exact:___
- 7. UnitTest sample public class UserTest extends UnitTest { private User user; void setUp() { this.user = User.GetSampleUser(); } void testUserSetName() { this.user.setName('John Doe'); this.assertTrue(this.user.name.length > 0); this.assertFalse(this.user.name == 'anonym'); this.assertEquals('John Doe', this.user.getName); } }
- 8. Functional test sample public class SearchTest extends FunctionalTest { function testFindResult() { this.openBrowser('firefox'); this.open('http://www.example.com', 30000); this.type("//input[@id='search-field']", "Harrr"); this.click("//fieldset/input[@type=submit]"); this.waitForPageToLoad(30000); this.assertTestPresent("regexp:\\d+ results found.*"); this.assertCookieExists('MySessionID'); } }
- 9. What you can test? Unittest: Levels: Function testing Feature testing System testing Functional test: Page elements Ajax jobs Javascript
- 10. Shortcomings in testing Testing GUI appearance Complicated system actions (e.g.: in specific cases) There is no setup and teardown on test suit level It's easily became slow Browser (un)capabilities frame / window handling security issues (file upload) best in FF (of course) If your code needs some conceptual change, likely your tests too Selenium sometimes collide with other JS frameworks (MooTools) UnitTest modify access to global variables, so sometimes those are unavailable
- 11. Why TDD is cool? You can fix the topmost (maybe all the) requirements Help to build a more stable software requirement Continuous code checking Prevent from writing test for code (the best: write code for the test)
- 12. Drupal and testing Drupal uses SimpleTest framework Bunch of helper to ease preparing environment for test for: create user login user post node Every core module has it's own module.test file Every core.inc has it's own test in simpletest module Unfortunately Drupal's Selenium module is unsupported now
- 13. Tips and tricks Try to cover all your code with tests Don't write test depend on other tests If one fails, it can ruin other tests (even good ones) Without dependency, every test could be called separately Never run tests on live site (neither live database dump) You can write a script to svn that runs the test suit before commit - prevent from commiting false code