Tautrimas Pajarskas, a PHP team lead and lecturer, emphasizes the importance of automated testing in legacy projects and encourages developers to start implementing it. The presentation covers types of tests, tools like CasperJS and PhantomCSS for testing, and provides a demo on writing basic tests and debugging. He advocates isolating legacy projects for testing and experimenting with unit testing frameworks to improve efficiency.

1. Tasting Your First Test
Burger
Tautrimas Pajarskas

2. About Me:
Tautrimas Pajarskas
PHP Team Lead,
Lecturer at NFQ Academy,
Striving for efficient and scalable
projects development

3. Goals Today
Observation: Automated testing is not used
with legacy projects.
My goal is to encourage you to start testing.
Today I will present you the HOW TO part.

4. What is Automated Testing?
Making someone do clicking for you (:

5. I am a Member of ONGR
We do Unit, Integration, Functional and
Acceptance testing. > 90% test coverage.

6. First Time Testing is Like Trying a
Burger
Too much stuff!

7. Continuous Integration
Example:
https://travis-ci.org/ongr-io/ongr-sandbox

8. Databases
Q: I want to test deleting a user. How to login
after that?
A: Use fixtures.
Q: ?

9. Which ones should I do?
Types of Tests

10. Tools
PHPUnit or phpspec?
Behat using Selenium or CasperJS?
Difficult to choose without guidance.

11. Advice:
Simply try CasperJS.
Acceptance testing.
And if you cannot experiment at work
Don’t do it at home!

12. Demo Time!

13. Demo Overview
1. Write basic CasperJS test
2. Test dynamic Bootstrap feature
3. Use Resurrectio recorder
4. Use PhantomCSS for design testing

14. Our Example Legacy Project

15. First Test

16. Taking a Screenshot for debugging

17. Fixing Desktop Viewport Size

18. Test Dropdown Menu Works

19. Try out Resurrectio
https://github.com/ebrehault/resurrectio
Resurrectio is a Chrome extension allowing to
record a sequence of browser actions and to
produce the corresponding CasperJS script.
-- Resurrectio README.md

20. Start the Recording

21. Resulting Script After a Few Clicks

22. PhantomCSS: CSS regression
testing
Let’s “accidentally” change <h1> font-size down

23. PhantomCSS: CSS regression
testing
PhantomCSS is good for detecting any visual
changes that are hard to sample using scripts.
Only do screenshot parts of the page.
Otherwise, the change in the footer will fail
every single page test in the test suite.

24. PhantomCSS: CSS regression
testing
Increasing number of screenshots can get large
for GIT. Use another GIT repo for them or look
up solutions offered in:
https://github.com/Huddle/PhantomCSS

25. PhantomCSS: CSS regression
testing
Use PhantomCSS only for design testing and
only where it is needed.
Otherwise, screenshot diff collision madness
will occur in your team (:

26. Summary

27. Summary for Legacy Projects
Isolate project’s testing version locally on a
separate vhost and a separate DB.
Write a script that prepares project for testing.
E. g. loads testing data for DB.
Start with highest level tests shown today.

28. Summary for Legacy Projects
Later, try out your Framework testing
functionality for Unit testing. You will need it for
much faster and fine grained tests. Remember
to delete and rewrite crappy tests!
Experiment, acquire testing skills and
spread the success stories!

29. Thank You!
Follow hottest web technology news at
facebook.com/nfq.lt