This is an open-ended contract opportunity for a full-time (40 hours per week) software testing professional. We are looking for deep functional testing of mission-critical web applications. We are looking for functional and business understanding as the first priority and then technical ability as the second. You will be a critical part of our overall development team.
Skills / Requirements
- Very good understanding of user thinking and what "makes sense"
- Strong software and web testing experience
- Strong technical aptitude, should be comfortable with using VPN
- Business acumen
- Usability understanding
- Work testing high traffic web portals and applications
- Light understanding of PHP / MySQL
- Scripting /automation understanding
- Load testing knowledge
- Testing experience on common security issues
We need someone who can dedicate themselves full-time to the project and be available on demand.
- Review of all functional specifications that we create. Every project has a functional spec - some are short and done via email, but most are 20-30 page documents that spell out what needs to be built. They can be enhancements or entirely new products/integrations. We build internal admin tools to manage our operations, as well as customer-facing web-based products/services.
- We generally have 3-4 projects going on at once. We strive to deploy to production every 3 weeks. Each project has its own functional spec. Each spec will contain numerous features, enhancements or fixes that must be done.
- We're very light on UI specs - we mostly document the functional side of things, and would sometimes include a sketch when needed. We don't have time for full blown UI specs or wireframing. So our QA is expected to understand our design standards, and ensure that new pages/features have the same consistent look and feel (in terms of UI and usability).
- We have 1 weekly development call, on Mondays at 9AM EST. Our QA always attends those.
- QA works closely with the development team. We have an internal team in Mauritius (9 timezones East of us). We also use a development team in the Philippines on a time/materials basis. The development teams interact with QA via Skype, email and DoneDone (bug tracking tool).
- We sometimes have critical issues on production which must be handled right away - the development team in Mauritius and myself will interact with QA to get a fix done with minimal downtime.
- As developers go through a functional spec, they'll often send a module that's deemed "completed" to QA for initial validation. They send instructions on how to test etc. (e.g., how to use some custom scripts to simulate test cases). The interaction is initially via email - but then any bugs/validation is done via DoneDone. QA logs bugs, assigns to the software team lead - that person then assigns to the individual developer. The developer and QA then go back and forth within DoneDone until the bug is resolved.
- When all the tasks in the functional spec are done, QA does overall testing on our test environment. This includes any regression testing (all other parts of the site). We have another cycle with developers within DoneDone for any bugs found.
- The specific parts of the code for this functional spec is then pushed to staging. The process repeats.
- The specific parts of the code for this functional spec is then pushed to production. The process repeats. Turnaround time for fixes is much shorter if critical/high priority bugs are found in production.
- QA also spends every day looking at key pages on our website - to make sure that nothing is broken.
- We would do the same process outlined in #8 and #9 above for new enhancements to internal admin tools.
- Our QA has to often look at our database tables to validate whether something is working properly or not - i.e., looking at the data that's saved. So there's always very low level data validation going on.
- QA would often comment on our functional spec, recommend better usability when it comes to user flows etc.
- QA pays attention to UI issues on the site. Makes sure the website looks good on tablets and mobile phones.
- QA would ideally do load testing, and security testing