Testing Practice @ My Company
QA History in My Company.
- Prior to YEAR [YYYY]
> No dedicated QA team
> Only developer testing and Peer testing of code
- From YYYY
> Started hiring qualified QAs
> Currently X Test lead and X testers
> Hiring going on
Project Management & QA
> JIRA/Greenhopper (Scrum interface) introduced to manage projects
> All requirements mapped as User Stories and Tasks in JIRA
> Bugzilla tickets also mapped to JIRA tickets
> QA team raises bugs against JIRA tickets
> Ensures issues are tracked properly.
QA Team
> X members and growing
> Prepares Test plan for each project
> Creates Test scenarios for each local QA release
> Conducts Functional testing based on Test scenarios
> Follows up with Regression testing for select features
> Logs issues against JIRA use case tickets as bug tickets
Creates Test Case documents (deliverable with each release)
> Conducts “Smoke testing” on Bugzilla tickets from client side
> Confirms presence of bug in current code
> Catches mismatch between customer expectations and developer understanding
> Conducted load testing on XXX using LoadRunner and Apache JMeter
Automated “nightly” build
- 12 hr automated build cycle (using Jenkins)
Pros
> Deploys latest code to local test server
> QA team does Functional testing on latest features
> This is followed by Regression testing on select features
> Static code analysis tool gives code quality report in dashboard (Sonar)
> Amalgamated result from multiple static code analysis tools
> Industry standard tool (used by all Apache projects)
Cons
> Currently auto-deployment feature only for XXXX
> Static code review shows false positives – sometimes makes developers ignore valid warnings
Steps to improve
> Introduce auto-build for all projects
> Auto deployment not happening for XXX – can be done easily
> Need to research auto build options for .NET projects
> Introduce compulsory weekly code review (peer review) for all projects
> From the past month we are conducting fortnightly sessions on CMMi processes.