Software testing
https://en.wikipedia.org/wiki/Software_testing
- Defects management & Quality Attributes
- vs Quality Management / Assurance
- Software Quality
- Snippet from Wikipedia: Software testing
Software testing is the act of examining the artifacts and the behavior of the software under test by validation and verification. 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. Test techniques include, but are not necessarily limited to:
- analyzing the product requirements for completeness and correctness in various contexts like industry perspective, business perspective, feasibility and viability of implementation, usability, performance, security, infrastructure considerations, etc.
- reviewing the product architecture and the overall design of the product
- working with product developers on improvement in coding techniques, design patterns, tests that can be written as part of code based on various techniques like boundary conditions, etc.
- executing a program or application with the intent of examining behavior
- reviewing the deployment infrastructure and associated scripts and automation
- take part in production activities by using monitoring and observability techniques
Software testing can provide objective, independent information about the quality of software and risk of its failure to users or sponsors.
Software testing can determine the correctness of software under the assumption of some specific hypotheses (see the hierarchy of testing difficulty below), testing cannot identify all the failures within the software. Instead, it furnishes a criticism or comparison that compares the state and behavior of the product against test oracles — principles or mechanisms by which someone might recognize a problem. These oracles may include (but are not limited to) specifications, contracts, comparable products, past versions of the same product, inferences about intended or expected purpose, user or customer expectations, relevant standards, applicable laws, or other criteria.
A primary purpose of testing is to detect software failures so that defects may be discovered and corrected. Testing cannot establish that a product functions properly under all conditions, but only that it does not function properly under specific conditions. The scope of software testing may include the examination of code as well as the execution of that code in various environments and conditions as well as examining the aspects of code: does it do what it is supposed to do and do what it needs to do. In the current culture of software development, a testing organization may be separate from the development team. There are various roles for testing team members. Information derived from software testing may be used to correct the process by which software is developed.: 41–43
Every software product has a target audience. For example, the audience for video game software is completely different from banking software. Therefore, when an organization develops or otherwise invests in a software product, it can assess whether the software product will be acceptable to its end users, its target audience, its purchasers, and other stakeholders. Software testing assists in making this assessment.
GitHub Topics
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.
Source: YouTube
ISTQB
External links:
Disciplines & Methodologies
Tools & Technologies
- Azure DevOps
- CMake
- codeBeamer
- Gauge
- Gerrit Code Review
- GitHub Copilot
- GitHub Learning Lab
- GitLab
- HP ALM
- Invoke-Build
- Jama
- Jenkins
- Microfocus
- Orcanos
- Postman
- Rally Software
- Rational solution for CLM
- Rational Team Concert
- ReQtest
- Selenium
- SoapUI
- SonarQube
- Team Foundation Server
- TeamForge
- Test automation
- Helix ALM (TestTrack)
- Visual Studio
- VSALM
- Visual Studio Team Services
Links
- GeeksforGeeks
- Good and Bad Technical Debt (and how TDD helps)
- Guru99
- List of tools for static code analysis
- Don't repeat yourself (DRY)
- EITBOK
- IEEE software life cycle
- Issue tracking system
- ISO/IEC 15504
- Technical Debt
- V-Model
Related:
## ToDo ##
- 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
- 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