Shift Left Testing is the name applied to the Agile concept to shift the software testing activities from the end of the software development life cycle to its beginning, or on the left of life cycle diagrams. In his article “Four Types of Shift Left Testing”, Donald Firesmith of the Software Engineering Institute discusses the importance of shift left testing and defines four different approaches to implement shift left testing.
Software testing is an important and tricky topic for mobile app development. With multiple operating systems versions and devices manufacturers, it is very time consuming to cover all possible combinations. This is why it is recommended to automate testing with a parallel perspective rather than performing tests sequentially. In this article, Tarik Demirović explains how to implement parallel mobile testing for Android devices with Appium.
Tired of projects where the wrong thing is tested? Finding TDD too time-consuming or too hard? High test coverage and your users still find bugs? Don’t understand if your tests are unit, integration, automation? InVEST in your future; come and discover how vertical slice technology helps to write those tests that matter.
Jasmine is an open source behavior-driven development (BDD) framework for testing JavaScript code. Angular is a development platform for building mobile and desktop web applications using Typescript/JavaScript (JS) and other languages. In his article, Gerard Sans offers a presentation of Jasmine, discusses the unit testing of AngularJS and shares some Unit Testing recipes for Angular 2: Components, Services, Http and MockBackend, Directives, Pipes, Routes, Observables and EventEmitter.
Years after Kent Beck provided JUnit, unit testing is part of most developer teams tooling. However, there is a trend that tends to threaten unit testing, claiming only integration testing can truly detects defects in software. This presentation first defines what unit testing and integration testing are, and their respective pros, cons and uses. Then, it explores the unique challenges posed by integration testing. Finally, tools and techniques are presented so that integration testing can become a true asset in each software developer bag of tricks.
Code coverage is a software testing metric that measures the degree to which the source code of a program is tested by a particular test suite. This metrics is often difficult to understand and interpret for software development teams. In this article, Eran Sher proposes a better approach to code coverage that is more adapted to the current situation of continuous delivery and service architecture.
The status of the testing phase and the role of the software tester are challenged and changing as organizations transition from a classical waterfall methodology to software development towards Agile approaches like Scrum. In his article “Reinventing Testers and Testing to prepare for the Future”, Patrick Prill shares his opinion about this situation and provides some hints for the evolution of software testing and the software tester role.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates