Slides from the Joomla! Day Germany 2016 https://www.youtube.com/watch?v=D3G30ED5820

1. Joomla! Testing
Yves Hoppe
@yveshoppe@compojoom

2. Why?
Deliver better and reliable application
Validate there is no regression
Make sure your application runs as expected
Trust your own application
Makes debugging much easier

3. Tests
In Joomla!
Unit tests
Integration tests
System tests
JavaScript tests
CodeStyle (phpcs)

4. Joomla! Automated Testing Team

5. Unit testing

6. In Unit testing()
we test a small and specific
amount of code

7. Sample method
public function isTheAnswer($number)
{
if ($number === 42)
{
return true;
}
return false;
}

8. Sample test
class TestCase extends PHPUnitFrameworkTestCase
{
public function testIsTheAnswer()
{
$this->assertTrue(isTheAnswer(42));
$this->assertFalse(isTheAnswer(1));
// … Best practice: One assertion per test
}
}

9. The issue / reality
public function getTheAnswer($number)
{
if (is_array($number))
throw new Exception('Arrays not accepted');
if (!is_numeric($number))
// Check
// Decimal, Binary, Hex - @todo add lower / upper case check
if ($number === 42 || $number === '00101010' || $number == '2A' || $number == '0x2A')
return '<span class="answer-right">The number is the answer to everything</span>';
elseif ($number == 13)
return '<div class="answer-partial">What do you get when you multiple 6 x 9=</div>';
elseif ($number == 666)
return 'WTF?!';
return false;
}

10. Benefits of
Unit testing
Issues can be discovered early
Acts as documentation
Forces you to write simpler and
more readable code
Verifies the design
Fastest and no GUI necessary

11. Drawbacks
Does not show the absence of
errors
Hard to set up useful and realistic
tests
Writing unit tests after the
development can be tough
Does only cover code

12. Unit tests in Joomla!

13. https://github.com/joomla/joomla-cms/tree/staging/tests/unit

14. PHPUnit 4.8.27
Within today 6119 different tests with 10526 assertions

15. We need you

16. Running the Joomla! unit tests
Clone the current staging repo from GitHub
git clone --depth 1 https://github.com/joomla/joomla-cms
Navigate with the command line to the cloned joomla instance
cd joomla-cms
Install dependencies with composer (get it before)
composer install
Run the tests with:

17. Value for Joomla! Extension Developers

18. Downsides
Complicated to set up with Joomla!
You have to mock and bootstrap everything
Lot of work

19. System Tests

20. In System Testing(Browser testing)
we test against the installed
and running application

21. Benefits
Tests the whole
application
Real world tests
Test more code with
less lines

22. System tests vs Unit tests
Unit tests are mainly used to test framework classes
System tests make sure the application works correctly from a user point
System tests does not require you to understand the code (or even the
programming language)
System tests test the whole system not only a small part
They also cover JavaScript, CSS and markup changes

23. System tests in Joomla!
https://www.youtube.com/watch?v=ZHo0TuA5Qjs

24. Google Summer of Code 2016
Prital Patel
● Setup of browser automated
tests for Joomla!
● Powered by Gherkin
● For com_users
● And com_content

26. Software used

27. https://github.com/joomla-projects/gsoc16_browser-automated-tests

28. Sample Codeception test
public function administratorCreateWeblink(StepAcceptanceweblink $I) {
$I->wantToTest('Weblink creation in /administrator/');
$I->doAdministratorLogin();
$I->amOnPage('administrator/index.php?option=com_weblinks');
$I->waitForText('Web Links', '30', ['css' => 'h1']);
$I->checkForPhpNoticesOrWarnings();
$I->clickToolbarButton('New');
$I->waitForText('Web Link: New', '30', ['css' => 'h1']);
$I->fillField(['id' => 'jform_title'], $this->title);
$I->fillField(['id' => 'jform_url'], $this->url);
$I->clickToolbarButton('Save & Close');
$I->waitForText('Web Links', '30', ['css' => 'h1']);
$I->see('Web link successfully saved', ['id' => 'system-message-container']);
$I->see($this->title, ['id' => 'weblinkList']);
}

29. Running the Joomla! Browser tests
Clone the current staging repo from GitHub
git clone --depth 1 https://github.com/joomla-projects/gsoc16_browser-
automated-tests
Navigate with the command line to the cloned instance codeception folder
cd gsoc16_browser-automated tests/tests/codeception
Install dependencies with composer (get it before)
composer install
Configure ‘tests/codeception/acceptance.suite.yml’ and run the tests with:

30. Value for Joomla! extension developers

31. Benefits
Fast to setup and you don’t need to mock Joomla!
JoomlaBrowser has common Steps for Joomla, like:
Installation, uninstallation of extensions
Navigation, Checking for PHP notices
Creating menu items

32. JavaScript Tests

33. In JavaScript Testing(Browser based)
We cover the JavaScript files
of our application.

34. JavaScript tests in Joomla!

35. Google Summer of Code 2016
Ruchiranga Wickramasinghe
● Setup of an automated test
system
● Coverage reporting
● For /media/system/js
● Tests are merged in Joomla!
Core now

36. Software used

37. Jasmine 2.4.1, Jasmine-jQuery 2.1.1, Karma 0.13.22 and Firefox 48
Within today we have 196 different tests

38. Running the JavaScript! tests
Clone the current staging repo from GitHub
git clone --depth 1 https://github.com/joomla/joomla-cms
Navigate with the command line to your joomla instance javascript tests folder
cd joomla-cms/tests/javascript
Install dependencies with npm (get it before)
npm install
Run the tests with:

39. Value for Joomla! Extension Developers

40. Benefits
No need for mocking Joomla!
No running Joomla! Installation needed
Easy to write and setup

41. CodeStyle tests

42. Code Style
and Metrics tests(Static Analysis)
check .

43. Why Code Style
matters
Communication is the Key
Code looks consistent
Clear rules for developers
Make Errors obvious

44. Code Style in Joomla!
http://joomla.github.io/coding-standards/
PHP_CodeSniffer
(phpcs)
and PHPQA Tools

45. PHP_CodeSniffer 1.5.6 (working on upgrade)

46. Running the PHP_CodeSniffer checks
Clone the current staging repo from GitHub
git clone --depth 1 https://github.com/joomla/joomla-cms
Navigate with the command line to your joomla instance
cd joomla-cms
Install dependencies with composer (get it before)
composer install
Run the tests with:

47. Automated testing

48. Putting the tests
together to a big
automatic safety net!

50. Why?
Repeatable
Detect issues for every commit / pull request
Saves you time and money

51. Automated tests in Joomla!

52. Software used

53. Directly see issues at your Pull Request

54. Runs for every change and pull request against core
Travis:
Multiple PHP Versions:
- PHP 5.3, 5.4, 5.5, 5.6, 7.0
- 7.1, HHVM (allowed to fail)
JavaScript tests (Node.js)
PHP_CodeSniffer (PHP 5.6)

55. Conclusion

56. Call for volunteers!
The Joomla! Automated Testing Working Group is looking for
new members, which want to make Joomla! better
https://volunteers.joomla.org/teams/automated-tests-working-group

57. Questions?
Thank you for listening!
@yveshoppe