When testing a web project, we check for four key things:
- Does it work correctly?
- Does it look right?
- Is everything else still working?
- Are there any security holes?
Each time a developer makes a change, it is sent to the lead developer for peer review. Once approved it is added to the code repository, which triggers a series of automated tests to check against all of the above criteria. By carefully describing how the site should function and then testing those functions, any issues are immediately picked up and resolved.
The hard thing about AI isn't making it. It's testing it to see if it actually works
Testing Machine Learning or AI powered features is often trickier than it seems
Testing web projects
One of the things we've started doing quite differently over the last few years is how we test our web projects
Automated vulnerability scanning for Ruby on Rails projects
Vulnerability scanning software Ruby on Rails analysis
A look inside our Jenkins Pipeline - how we make reliable stuff
How we build relational trust; our integrated testing pipeline
How a project gets tested and deployed with GitFlow
GitFlow is the way of the future. Find out why and how here.