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 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 & automation
- take part in production activities by using monitoring & observability techniques
Software testing can provide objective, independent information about the quality of software and risk of its failure to users or sponsors.
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
- Feature toggle
- Software deployment
- Software development process
- Software documentation
- Software quality assurance
- Software quality management
- SQALE
- Static program analysis
- Test-driven development
- Unit testing
Tools & Technologies
- Azure DevOps
- CMake
- codeBeamer
- Gauge
- Gerrit Code Review
- 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
Todo:
* Appium
- AutoIt
- Behat
- BrowserStack
- Bugwolf
- Burp Proxy
- CA Test Data Manager
- CasperJS
- Cobertura
- Codacy
- CodeFactor
- CodeScene
- Concordion
- CrossBrowserTesting
- Cucumber
- Cucumber.js
- Cyara Velocity
- Cypress.io
- FitNesse
- Flood.io
- Gatling
- Gauntlt
- GenRocket
- Google Test
- HttpMaster
- Inspec
- JMeter
- JUnit
- Jasmine
- Karate
- Karma
- Katalon Studio - Intelligent Test Automation
- Locust
- Micro Focus LoadRunner
- Micro Focus Unified Functional Testing (UFT)
- Mocha
- NUnit
- Nightwatch.js
- Parasoft API Test
- Parasoft Development Testing Platform
- Parasoft Environment Manager
- Parasoft SOATest
- Parasoft Virtualize
- Perfecto Continuous Quality Lab
- Protractor
- QF-Test
- Qualitia Automation Studio
- Qunit
- Ranorex
- Rational Integration Tester
- Rational Quality Manager
- Robot Framework
- Sahi
- Sauce Labs
- Screenster
- Selenium
- Smartbear SoapUI
- SoapUI
- SpecFlow
- Squash TA
- Squash TM
- Test Architect
- TestComplete
- TestNG
- TestObject
- TestRail
- Tricentis Tosca
- Watir
- pytest
- xUnit.net
- Selenium
- Cucumber Testing
- SoapUI
- Agile Testing
- JUnit