Intermediate automated front end testing for developers
How it currently works, think of this as common deployment releases on a calendar basis.
See Freelance design / development cycle in slideshow on her website
Types of Tests
Testing Players
- QA
- Dev
- Product Owners
Black Box Testing?
- Hide the Code and Refresh
White Box Testing
- Transparent you know how it works (reading code and understanding of it)
Unit Testing
- Breaking code into small chunks for testing
- Software that tests Software
Integration Testing
- Does everything work together as a group of functions, plugins, dependencies etc.
Functional Testing
- Testing for specific functions, etc. automated process such as a wizard to do tasks.
Systems Testing
End to End Testing
- Similar to System but between various elements like databases communication or geographical locations
Sanity Testing
- Does it work at least a little bit?
Regression Testing
- Does it still work as expected after another modification (aka functions edit or plugin added)
Acceptance Testing for End of Project and Delivery
- Does it meet client/user needs,
- does the client think it works as expected
- This is important to close the project
- Once closed they should pay for further updates
- Most important for paycheck and delivery of project
Stress Testing
- Can more than a few people use it at the same time?
Usability Testing
- Testing to see if it is user friendly before and after a project begins (physical mockups before development and testing afterwards)
Automation
- Methods to reduce manual tests and data entry
- “Write Code to Test Code”
- example: PHPUnit
Testing
- Selenium IDE - Firefox Plugin
example: A client wants to change all instances of a word to another word or phrase (company name change)
- create a filter to change items you wouldn’t always catch with your eyeballs
Tool
Jenkins is a award-winning app that uses a cron job to automate and monitor executions
Tabby Chapman
@tabbymarie
www.tabbychapman.com
