Code Reviews for Test Automation Code
For software developers, the Code Review process has been essential for ages, but they can also be used in software testing when you create test automation code.
Software Testing Videos and Tutorials: Load Testing, Unit Testing, Functional Testing, Performance Testing, Agile Testing, DevOps
For software developers, the Code Review process has been essential for ages, but they can also be used in software testing when you create test automation code.
Test Engineering culture emphasises on quality ownership by all involved in a project and redefines the role of testers as engineers as quality enablers instead of gate keepers. This talk shares the experience to build a test engineering culture across the organization, how does it vary with the size of the team and the company and the role of software testersin building this culture by enabling others with tools and processes for quality improvements.
Mockito is a popular and powerful open source Java mocking framework. In order to achieve good unit tests, you need to make use of mocks and stubs. And that’s exactly what this talk will be about: What is a mock?
Most research on Agile Testing and QA have requirements on highly automated testing/CI and an Agile or Scrum project-management structure. How can we iterate towards a more Agile testing process, with all the benefits that entails, when some of the common requirements are missing or undesirable in the near-term?
How good are your test cases? Maybe they are good, or maybe you need to add some new ones. How to tell? You can measure things like code coverage to check if some parts of your code were not executed. Still, this does not tell you anything about the quality of your assertions and your software testing results. In the extreme case, a test suite with no assertions might still achieve 100% code coverage, although being of questionable value.
This presentation will show you why the testing pyramid need to be very wide. You will understand why this is an absolute necessity if all possible paths through the application should be tested. In other words, let me show you why your tests must be very shallow.
Although Behavior Driven Development has been existing for over 10 years, the methodology hasn’t yet been very popular in the Java world. One reason for this are the existing BDD tools for Java that are cumbersome for developers to use and require a lot of maintenance.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates