The following are some generic rules that are valid for any unit test and not just PHPUnit:
• Independent: Each test needs to run independently from other tests
• Fast: To have useful tests and be able to run them as often as possible
(for example, as pre- or post-commit hooks), tests need to be fast.
• Repeatable: You should be able to run a test as many times as you want with the same result.
• Up to date: Tests are written once, but code can be changed or extended. If you are not going to keep tests up to date, the initial investment in tests will be just a waste of time and money. The rule is, whoever breaks the test, fixes the test.
• Short: Tests should be just a few lines—easy to read and understand.
• Resilient: Once written, tests shouldn’t change till the behavior of tested
PHPUnit Essentials – by Zdenek Machek
You like tracking things, projects, tasks and progress? Alone or within a team?
You heard or you are familiar with Agile development?
JIRA is the tool for you.
Continue reading Working With JIRA – Brief Breakdown
After you spending some time coding and developing, sooner or later you will encounter something called TDD (Test-Driven Development) . Continue reading Testing this testing that?
In this interview, Elliotte Rusty Harold discusses the true meaning of PUT and DELETE. Continue reading Why PUT and DELETE? REST part 2
Wife: Who is “Roy Fielding”?
Ryan: Some guy. He’s smart.
Wife: Oh? What did he do?
Ryan: He helped write the first web servers and then did a ton of research explaining why the web works the way it does. His name is on the specification for the protocol that is used to get pages from servers to your browser. Continue reading “How I Explained REST to My Wife” REST part 1