Almost every software development agency eventually creates a QA department. QAs' play role is to validate if the product meets both business and technical requirements, but also works and looks as expected.
Almost every software development company eventually creates a QA department. Software tester's role is to validate whether the product meets both business and technical requirements, but also that it works and looks as expected. Yes, a company can do just fine with no testing experts, and make their developers take care of that part. However, if you crave an effective, automated testing process, you need real pros in your team.
Having established workflows and knowledge how to make things done, a question about increasing qualifications and certifying the workers arises. Undeniably, product quality is one of the main targets in each development cycle both for the software development company and the client. It's obviously not just a QA's job to provide that, but having a professional quality assurance tester increases your chances of success.
We decided to broaden our skills and acquire ISTQB certifications for 2 main reasons:
During the investigation of the software quality certification market, we came across different options: ISEB119, IIST65, QAI and ISTQB. After analyzing them, we came to the conclusion that the ISTQB certificate satisfies us the most: it is universal, well known, and covers a big volume of testing area. We also apply ISO 25010 to several of our projects.
Doug Talbot presents a study of how organizational values and behaviours were used to transform HR processes for recruitment, performance management and professional development.
This talk was given as part of a live-stream with QA Babble, presented by Woodrow Mercer. Testing Without the Safety Net - Tom McCrawley Lots of people have
Shorter development cycles and faster innovation are the basic characteristics of the DevOps model. It has swept the market with new ideas and incredible solutions, leading to 74% adoption by global enterprises. The reasons are different, but the top ones are the ability to recover from a failure in less than 60 minutes, minimization of support cases by 37%, and overall need to “put out fires”. No wonder that Quality Assurance, as a stage of the software development process, had to adapt to the new reality of the DevOps model and change its traditional approaches.
We’re exploring the importance of software testing in software startups and looking for a way to balance product quality with a fast time-to-market.
Jem Djelal discusses the difference between a safe space and a brave one, how to distinguish between them, the pros & cons, how to move from a safe to a brave space, and patterns to use.