Quality Engineering

In software projects, especially those with longer timelines and higher complexity in business rules and/or changes, it’s common to require a better structured test plan to provide visibility over the scope of changes, business rules, and what will be tested. In many cases, one person on the team is responsible for executing all scenarios and documenting bugs. However, this is a great opportunity for QA to foster collaboration among team members, promoting knowledge sharing about a specific feature and strengthening the team’s quality culture and the feeling that “Quality is everyone’s responsibility.” ...

Introduction Writing about the role of QA in software development teams is crucial to understanding the evolution of the area and the importance of moving away from the old perception that QA is limited to only “testing software”. This article aims to clarify the differences between the roles of Tester, QA (Quality Assurance) and QE (Quality Engineer) and challenges faced by a QA professional within a development team. Differences between Tester, QA and QE Tester is the more traditional and general used term and is more directly associated with performing manual tests. This function focuses on identifying bugs or defects in software, often operating at the end of the development cycle. The tester checks the product’s compliance with the established requirements, but his performance is generally reactive — he acts after the product or functionality has already been developed. ...