A collection of public resources about how software companies test their software
-
Updated
Dec 20, 2024 - HTML
Software testing is the act of examining the artifacts and the behavior of the software under test by validation and verification to make sure it works. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Testing can be iterative, and happen multiple times.
A collection of public resources about how software companies test their software
A payment application to demonstrate real-world usage of Cypress testing methods, patterns, and workflows.
This repository contains General Test Cases for performing Manual Testing on the Web/Mobile application. It also has Test cases related to API Testing. Templates related to Test Plan and BugBash are also updated.
🚀 A curated list of awesome testing tools 🚀
📝 A demo todo/notes app which demonstrates the use of MVVM architecture with Test-cases, Navigation Component Library, Room Database, LiveData, Coroutines, Datastore etc.
🐂 Simple and complete custom Selectors for Testcafe that encourage good testing practices.
A crowdsourced testing course, written by testers for testers wannabes.
Automation tool to write tests for Http Api, Web Page Action, and Command Line based application with embedded mock server and highly configurable reports
AngularJS 1.4x and ES6 application boilerplate /w testing practices using Webpack
Different approaches to mocking the Date in Jest tests
🆔 Graduation project. UI and API automated tests using Java / Selenide / REST-Assured
Describing the processes used by the Infinum QA Team
Example for Android application test-suite - Unit tests with JUnit, UI tests with Espresso
Collection of free open source software testing tools with some links on how to use them
🥒 Quick start for testing with Cucumber.js
Nginx application showcasing how to do lightweight tests with ruby rspec
Helping test "any" code in readme with GitHub Action. All you need is unit testing synchronized external files in the ordinary way.
Evolving idea of something I call QA Fortress.