test automation | TechWell

test automation

Test pyramid 5 Reasons You Should Have More Unit Tests

The test pyramid is a valuable visual in agile. In particular, it argues that unit tests should make up the majority of tests, and while agile teams recite this principle, it is often not clear why it is so important. Here are five reasons unit tests should make up the majority of tests written for an application.

Jeffery Payne's picture
Jeffery Payne
Image of a person's face made out of code Designing a Smart QA Strategy

With increasingly complex and sophisticated technologies being used in testing, quality has to become a smart activity. A smart QA strategy is both about building smart models and making smart choices. We must keep in mind the balance between manual and automated solutions and which are needed to accomplish our goals.

Mukesh Sharma's picture
Mukesh Sharma
Microphone on stage at a software conference 4 Takeaways from Agile + DevOps East 2018

With a week full of sessions, tutorials, training classes, and events, the Agile + DevOps East software conference had plenty of takeaways. Here are four highlights, including discussions about agile estimation, finding your ideal job, some challenges to advancing test automation, and leading self-organizing teams.

Owen Gotimer's picture
Owen Gotimer
Icon showing the phases of continuous testing Continuous Testing Is Not Automation

Many people confuse continuous testing with test automation. That makes sense, because you cannot do continuous testing without automated tests. But it is much more. Continuous testing has a higher-level maturity that could require a totally different way of working—but it also gives a faster path to production.

Adam Auerbach's picture
Adam Auerbach
Microphone on a stage at a conference Lessons Learned (and Unlearned) at STARCANADA 2018

With a week full of sessions, tutorials, training classes, and events, the STARCANADA software testing conference had plenty of takeaways. Some highlights: what jobs will look like in the future with AI, why testers should lead efforts to make quality everyone's responsibility, and the importance of unlearning.

Owen Gotimer's picture
Owen Gotimer
man carrying bag of debt How Are You Managing Your Test Debt?

Just as debt can be good and bad in everyday life (such as a home mortgage), debt in the engineering world can also be good and bad. This applies to quality engineering as well—with good and bad test debt. As testers, how do we create a balance and stay at the right test-debt quotient?

Rajini  Padmanaban's picture
Rajini Padmanaban
Microphone on a stage for a keynote presentation 4 Lessons from the STARWEST 2018 Keynote Presentations

With a week full of sessions, tutorials, training classes, and events, the STARWEST software testing conference had plenty of takeaways useful for your professional and personal life. Here are four lessons distilled from the conference’s keynote presentations on testing, communication, and directing your career.

Owen Gotimer's picture
Owen Gotimer
puzzle Writing Tests: Action Abstraction

Keywords have become a popular way of writing tests. Hans Buwalda used keywords to devise the Action Based Testing method in which tests are written as sequences of “actions” represented with keywords. However, keywords are just a physical representation of actions, and there are other ways to do this.

Hans Buwalda's picture
Hans Buwalda