Differences

This shows you the differences between two versions of the page.

@@ 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, from basic design to final deployment. This method assists in identifying and resolving difficulties early in the development process, lowering the chance of costly errors and delays.
+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, ALM and DevOps software testing can help to minimize the entire cost of software development and maintenance. Developers can save time and resources by identifying and addressing issues early in the development process, as well as reducing the possibility of costly errors or delays in the program.
+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://en.wikipedia.org/wiki/Software_testing
+  * Defects management & Quality Attributes
+  * vs Quality Management / Assurance
+  * Software Quality
+  * [[microsoft:azure:testplans|Azure Test Plans]]
+  * [[devops:verify|DevOps Verify]]
+  * [[Code Coverage]]
+<accordion>
+<panel type='' title='What is software testing?'>
+Software testing is the process of verifying and validating software to ensure that it meets the desired requirements and quality standards.
+</panel><panel type='' title='Why is software testing important?'>
+Software testing is important because it helps to identify defects and errors in software, improve the quality of software, and reduce the risk of software failure.
+</panel><panel type='' title='What are some common types of software testing?'>
+Some common types of software testing include unit testing, integration testing, system testing, acceptance testing, and regression testing.
+</panel><panel type='' title='What is the difference between manual and automated testing?'>
+Manual testing is the process of testing software manually, using human testers to execute test cases and identify defects. Automated testing is the process of testing software using automated scripts or tools to execute test cases and identify defects.
+</panel><panel type='' title='What are some common testing techniques used in software testing?'>
+Common testing techniques used in software testing include black-box testing, white-box testing, gray-box testing, boundary value analysis, equivalence partitioning, and error guessing.
+</panel><panel type='' title='What is the purpose of test cases in software testing?'>
+Test cases are used to define the steps and expected results of a particular test scenario in software testing. They help to ensure that testing is performed consistently and thoroughly, and that defects and errors are identified and addressed.
+</panel><panel type='' title='What is the role of a test plan in software testing?'>
+A test plan is a document that outlines the scope, objectives, approach, and resources of a software testing project. It helps to ensure that testing is planned, organized, and executed effectively.
+</panel><panel type='' title='What is continuous testing?'>
+Continuous testing is the practice of testing software continuously throughout the software development lifecycle, using automated testing tools and techniques. It helps to identify defects and errors early in the development process, and ensures that software is delivered with the desired quality and performance.
+</panel><panel type='' title='What is exploratory testing?'>
+Exploratory testing is the process of testing software without predefined test cases or scripts, using the tester's intuition and experience to identify defects and errors. It can be used to complement other testing techniques, and is particularly useful for finding defects that are difficult to identify using scripted testing.
+</panel><panel type='' title='What is the difference between functional and non-functional testing?'>
+Functional testing is the process of testing software to ensure that it meets the functional requirements, or what the software is supposed to do. Non-functional testing is the process of testing software to ensure that it meets the non-functional requirements, or how well the software performs in terms of factors such as performance, security, usability, and reliability.
+</panel></accordion>
+<callout type="primary" title="" icon="fa fa-rss">
+<btn type="primary"  icon="fa fa-rss">[[Software Testing RSS Feeds]]</btn>
+</callout>
+----
+{{wp>Software_testing}}
+<callout type="" title="GitHub Topics" icon="fa fa-github">
+  * https://github.com/topics/testing
+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.
+</callout>
+<jumbotron>
+<WRAP group>
+<WRAP row>
+{{youtube>cDQ34z0oqnQ?full}}
+</WRAP>
+<WRAP row>
+<WRAP column right><wrap lo>Source: [[https://www.youtube.com|YouTube]]</wrap></WRAP>
+</WRAP>
+</WRAP>
+</jumbotron>
+===== ISTQB =====
+  * https://www.istqb.org/
+<callout title="External links:">
+  * https://www.guru99.com/test-management.html
+</callout>
+===== Disciplines & Methodologies =====
+{{topic>method?test&simplelist&nodate&nodesc&nouser&sort}}
+===== Tools & Technologies =====
+{{topic>tools?test&simplelist&nodate&nodesc&nouser&sort}}
+===== Links =====
+{{topic>links?test&simplelist&nodate&nodesc&nouser&sort}}
+{{topic>kb?test&simplelist&nodate&nodesc&nouser&sort}}
+{{tag>governance development }}
+<callout type="primary" title="Related:">
+{{topic>test}}
+</callout>
+=== ## ToDo ## ===
+  * FIXME - [[:about|Support Us...]] ->
+  * 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://www.istqb.org/
+  * 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
+  * Test Planning and Management
+  * Test Case Design and Execution
+  * Test Automation
+  * Functional Testing
+  * Non-Functional Testing
+  * Regression Testing
+  * Integration Testing
+  * System Testing
+  * Acceptance Testing
+  * Performance Testing
+  * Security Testing
+  * Usability Testing
+  * Exploratory Testing
+  * Test Reporting and Metrics
+  * Defect Management
+  * Test Environment Management
+  * Test Data Management
+  * Test Process Improvement
+  * Test Automation Frameworks
+  * Continuous Testing
+  * Shift-Left Testing
+  * Test-Driven Development (TDD)
+  * Behavior-Driven Development (BDD)
+  * Test Coverage
+  * Test Design Techniques
+  * Risk-Based Testing