no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| Previous revision Next revision | |||
| — | test:test [2023/03/24 16:18] – Henrik Yllemo | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~NOCACHE~~ | ||
| + | ====== Software testing ====== | ||
| + | Software testing is an essential component of the software development life cycle (SDLC) for ensuring that software programs satisfy the desired quality requirements. Software testing is an important procedure in ALM (Application Lifecycle Management) and DevOps that helps to ensure that software is built, tested, and deployed quickly and efficiently. | ||
| + | |||
| + | ALM and DevOps are concerned with continuous delivery and continuous testing, in which software is tested at every stage of development, | ||
| + | |||
| + | One of the primary advantages of software testing in ALM and DevOps is that it helps to ensure that software applications are of high quality and satisfy the required specifications. Developers can identify and repair flaws before they become serious problems by testing the software at each stage of the development process, lowering the chance of costly errors and delays. | ||
| + | |||
| + | Another advantage of ALM and DevOps software testing is that it can help to increase the speed and efficiency of software development. Developers can save time and resources while reducing the chance of errors or faults in software by employing automated testing tools and techniques. | ||
| + | |||
| + | Furthermore, | ||
| + | |||
| + | Software testing is an important procedure in ALM and DevOps since it helps to verify that software applications are of high quality, efficient, and cost-effective. Developers can save time, cut expenses, and improve the overall quality and performance of software systems by leveraging automation technologies and processes. | ||
| + | |||
| + | https:// | ||
| + | * Defects management & Quality Attributes | ||
| + | * vs Quality Management / Assurance | ||
| + | * Software Quality | ||
| + | * [[azure: | ||
| + | * [[devops: | ||
| + | * [[Code Coverage]] | ||
| + | |||
| + | |||
| + | <callout type=" | ||
| + | |||
| + | <btn type=" | ||
| + | |||
| + | </ | ||
| + | ---- | ||
| + | |||
| + | {{wp> | ||
| + | <callout type="" | ||
| + | * https:// | ||
| + | |||
| + | Testing is the practice of systematically testing software to make sure it works. Testing can be iterative, and happen multiple times. | ||
| + | |||
| + | Eliminate bugs and ship with more confidence by adding these tools to your workflow. | ||
| + | </ | ||
| + | |||
| + | |||
| + | < | ||
| + | <WRAP group> | ||
| + | <WRAP row> | ||
| + | {{youtube> | ||
| + | </ | ||
| + | |||
| + | <WRAP row> | ||
| + | <WRAP column right>< | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | |||
| + | </ | ||
| + | |||
| + | ===== ISTQB ===== | ||
| + | |||
| + | * https:// | ||
| + | |||
| + | <callout title=" | ||
| + | * https:// | ||
| + | </ | ||
| + | |||
| + | ===== Disciplines & Methodologies ===== | ||
| + | {{topic> | ||
| + | ===== Tools & Technologies ===== | ||
| + | {{topic> | ||
| + | ===== Links ===== | ||
| + | {{topic> | ||
| + | |||
| + | {{topic> | ||
| + | |||
| + | |||
| + | {{tag> | ||
| + | |||
| + | |||
| + | <callout type=" | ||
| + | {{topic> | ||
| + | </ | ||
| + | |||
| + | === ## ToDo ## === | ||
| + | * FIXME | ||
| + | * Agile Testing | ||
| + | * API Testing Tools | ||
| + | * Appium | ||
| + | * Application Security Testing (AST) | ||
| + | * Application Testing Services | ||
| + | * AutoIt | ||
| + | * Behat | ||
| + | * BrowserStack | ||
| + | * Bugwolf | ||
| + | * Burp Proxy | ||
| + | * CA Test Data Manager | ||
| + | * CasperJS | ||
| + | * Cobertura | ||
| + | * Codacy | ||
| + | * CodeFactor | ||
| + | * CodeScene | ||
| + | * Concordion | ||
| + | * CrossBrowserTesting | ||
| + | * Cucumber | ||
| + | * Cucumber Testing | ||
| + | * Cucumber.js | ||
| + | * Cyara Velocity | ||
| + | * Cypress.io | ||
| + | * Defect Tracking | ||
| + | * Dynamic Application Security Testing (DAST) | ||
| + | * FitNesse | ||
| + | * Flood.io | ||
| + | * Functional Testing Tools | ||
| + | * Gatling | ||
| + | * Gauntlt | ||
| + | * GenRocket | ||
| + | * Google Test | ||
| + | * HttpMaster | ||
| + | * https:// | ||
| + | * Inspec | ||
| + | * Jasmine | ||
| + | * JMeter | ||
| + | * JUnit | ||
| + | * Karate | ||
| + | * Karma | ||
| + | * Katalon Studio - Intelligent Test Automation | ||
| + | * Load Testing Tools | ||
| + | * Locust | ||
| + | * Mainframe Testing Tools | ||
| + | * Micro Focus LoadRunner | ||
| + | * Micro Focus Unified Functional Testing (UFT) | ||
| + | * Mobile App Testing Tools | ||
| + | * Mocha | ||
| + | * Nightwatch.js | ||
| + | * NUnit | ||
| + | * Parasoft API Test | ||
| + | * Parasoft Development Testing Platform | ||
| + | * Parasoft Environment Manager | ||
| + | * Parasoft SOATest | ||
| + | * Parasoft Virtualize | ||
| + | * Perfecto Continuous Quality Lab | ||
| + | * Performance Testing Tools | ||
| + | * Protractor | ||
| + | * pytest | ||
| + | * QF-Test | ||
| + | * Qualitia Automation Studio | ||
| + | * Qunit | ||
| + | * Ranorex | ||
| + | * Rational Integration Tester | ||
| + | * Rational Quality Manager | ||
| + | * Robot Framework | ||
| + | * Sahi | ||
| + | * Sauce Labs | ||
| + | * Screenster | ||
| + | * Selenium | ||
| + | * Service Virtualization | ||
| + | * Smartbear SoapUI | ||
| + | * SoapUI | ||
| + | * SpecFlow | ||
| + | * Squash TA | ||
| + | * Squash TM | ||
| + | * Test Architect | ||
| + | * Test Automation Tools | ||
| + | * Test Data Management | ||
| + | * Test Management Tools | ||
| + | * TestComplete | ||
| + | * TestNG | ||
| + | * TestObject | ||
| + | * TestRail | ||
| + | * Tricentis Tosca | ||
| + | * Watir | ||
| + | * xUnit.net | ||