Profile cover photo
Profile photo
Software Testing Magazine
135 followers -
Software Testing Magazine: Unit, Functional and Load Testing Tools, News and Resources
Software Testing Magazine: Unit, Functional and Load Testing Tools, News and Resources

135 followers
About
Posts

Post has attachment
JUnit5 (JUnit Lambda) is a project to update the de facto standard tool in Java unit testing. This session describes how the JUnit framework has evolved to enable the modern features of the JVM as well as the underlying architectural changes that make JUnit5 ready for the modern era of Java.
Add a comment...

Post has attachment
A Coach’s Guide to Agile Testing is part of the nice series proposed to Agile coaches by Samantha Laing and Karen Greaves. This book provides a complete plan to run a workshop where members of a Scrum team can understand and learn the concepts behind Agile Testing.
A Coach Guide to Agile Testing
A Coach Guide to Agile Testing
softwaretestingmagazine.com
Add a comment...

Post has attachment
Serverless is more than a cloud computing execution model. It changes the way we plan, build, and deploy apps. But it also changes the way we test our apps.
Add a comment...

Post has attachment
As writing tests for frontend has always been hard, this presentation shows you how to make software testing easier in Angular applications. From unit testing components and services to end-to-end testing your entire application, this video will give you tips and techniques for testing in the latest versions of Angular using the Jasmine and Karma open source javascript testing tools. #angular #javascript #angularjs #softwaretesting
Add a comment...

Post has attachment
The Axway Automated Testing System (ATS) is a powerful multipurpose open source testing framework suitable for different types of functional, performance and UI testing of modern enterprise products. ATS allows interacting with tested applications in variety of ways, as well as preparing the test environment and verifying the actual results. #softwaretesting #opensource
Add a comment...

Post has attachment
This tutorial show you how to use the open source JUnit testing tool for Java to do Test-Driven Development (TDD). The promise of Test-Driven development is better software by thinking through how you want to test it, THEN writing code. At a high-level, you write enough of your class so that it runs. Then you think through how the class should work, and write test cases to test it. The test cases all fail because there’s no code. Finally, you write code until the test cases pass. And you’re done. So the testing of the software drives the entire process, which is why it’s called Test-Driven Development. #agiletesting #java
Add a comment...

Post has attachment
Behavior-Driven Development (BDD) is an Agile testing approach where you write human-readable sentences describing the features of your application and how they should work. Then you implement this behavior using a tool that produces automated tests to verify that the feature is implemented correctly. Open source .NET BDD tools like SpecFlow are used to store the requirements as live documentation and to perform functional or acceptance tests. #softwaretesting #dotnet #csharp
Add a comment...

Post has attachment
Page-Object pattern is very commonly used during software testing when you use test automation frameworks. However, as the scale of the framework grows, there is a limitation on how much reusability really happens. It can inherently become very difficult to separate the test intent from the business domain. This presentation discusses the issues with the Page-Object pattern and the solution that you can implement – Business Layer – Page – Object pattern, to help your code staying DRY. #softwaretesting
Add a comment...

Post has attachment
In an agile world where software never "stabilizes", tests can quickly move from being a pillar of quality to a burden and hindrance to change. Approval Testing mitigates this risk by removing the need for explicit assertions and instead managing changes to the system behaviour.
Add a comment...

Post has attachment
And as for the tester identity change per se (the way I’ve seen it which is 100% subjective), I think there was a very interesting metamorphosis the last 10 years. Testers did not want to be the “passive receivers” of developer’s work anymore, so there was a lot of talk about being an inspiration/guide/ambassador of quality. And that time created plenty of “empty” testers, the ones without strong knowledge and expertise, but with an ambition of some special knowledge and (at last!!!) power. This attitude couldn’t possibly sustain itself long. So naturally the emptiness started filling up with real expertise. But this time it was important to become an equal player of the development process. Which means testers having their own domain of expertise and at the same time share it with everyone else in the team. Not an easy task. But we seem to be managing.
Add a comment...
Wait while more posts are being loaded