Types of Software testing
Functionality Testing : The functionality of the application ( i.e GUI components ). against the specifications ( eg, if we click " submit" button, the application should display ..... " confirmation dialog box")
Acceptance testing: Formal testing conducted to determine whether a system satisfies its acceptance criteria and thus whether the customer should accept the system.
Regression Testing: Testing the application for checking whether the previous features are working properly or not, after adding new features to the application.
Stress Testing: The idea of stress testing is to find the breaking point in order to find bugs that will make that break potentially harmful.
Load Testing: This is merely testing at the highest transaction arrival rate in performance testing to see the resource contention, database locks etc...
Black-box Testing: Focuses on the program's functionality against the specification.
White-box Testing: Focuses on the paths of logic.
Unit Testing: The most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.
Integration Testing - testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.
Incremental Integration Testing: Continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.
Functional Testing: Black-box type testing geared to functional requirements of an application; this type of testing should be done by testers.
System Testing: Black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.
Sanity Testing: Typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.
Performance Testing: This term is often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.
Usability Testing: Testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.
Installation/Uninstallation Testing: Testing of full, partial, or upgrade install/uninstall processes.
Security Testing: Testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques.
Compatability Testing: Testing how well software performs in a particular hardware/software/operating system/network/etc. environment.
Ad-hoc Testing: Testing the application in a random manner.
Alpha Testing: Testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.
Beta Testing: Testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.
Showing posts with label agile automation testing. Show all posts
Showing posts with label agile automation testing. Show all posts
What is Agile Testing?
What is Agile Testing?
Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm.
Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm.
What are Agile practices?
What are Agile practices?
–> Test Driven Development (TDD)
–> Behavior Driven Development (BDD)
–> Continuous Integration
–> Pair Programming
–> Planning poker
–> Test Driven Development (TDD)
–> Behavior Driven Development (BDD)
–> Continuous Integration
–> Pair Programming
–> Planning poker
What are Agile Methods?
What are Agile Methods?
–> Agile Modeling
–> Scrum
–> Agile Unified Process (AUP)
–> Agile Data Method
–> Essential Unified Process (EssUP)
–> Extreme programming (XP)
–> Feature Driven Development (FDD)
–> Getting Real
–> Open Unified Process (OpenUP)
–> Lean software development
–> Agile Modeling
–> Scrum
–> Agile Unified Process (AUP)
–> Agile Data Method
–> Essential Unified Process (EssUP)
–> Extreme programming (XP)
–> Feature Driven Development (FDD)
–> Getting Real
–> Open Unified Process (OpenUP)
–> Lean software development
What are the Advantages of Agile Methodology?
What are the Advantages of Agile Methodology?
–> Customer satisfaction by rapid, continuous delivery of useful software
–> Working software is delivered frequently (weeks rather than months)
–> Face-to-face conversation is the best form of communication
–> Close, daily cooperation between business people and developers
–> Working software is the principal measure of progress
–> Continuous attention to technical excellence and good design
–> Simplicity
–> Regular adaptation to changing circumstances
–> Self-organizing teams
–> Projects are built around motivated individuals, who should be trusted
–> Even late changes in requirements are welcomed (this does not mean code & run.
Instead removing an existing feature or moving a deadline forward to accommodate late/unplanned feature requests
–> Customer satisfaction by rapid, continuous delivery of useful software
–> Working software is delivered frequently (weeks rather than months)
–> Face-to-face conversation is the best form of communication
–> Close, daily cooperation between business people and developers
–> Working software is the principal measure of progress
–> Continuous attention to technical excellence and good design
–> Simplicity
–> Regular adaptation to changing circumstances
–> Self-organizing teams
–> Projects are built around motivated individuals, who should be trusted
–> Even late changes in requirements are welcomed (this does not mean code & run.
Instead removing an existing feature or moving a deadline forward to accommodate late/unplanned feature requests
What is Agile software development ?
What is Agile software development ?
Adaptable software creation, also known as agile software development. Agile development is a style of software development that emphasizes customer satisfaction through continuous delivery of functional software. Based on a variety of iterative development disciplines including extreme programming (XP), agile methods put developers to work in small teams to tight budgets and short timescales. In contrast to traditional software development methods, agile developers liaise continuously with business clients, aiming to deliver working software as frequently as every two weeks during a project, and welcome changes to the requirement in response to evolving business needs
Adaptable software creation, also known as agile software development. Agile development is a style of software development that emphasizes customer satisfaction through continuous delivery of functional software. Based on a variety of iterative development disciplines including extreme programming (XP), agile methods put developers to work in small teams to tight budgets and short timescales. In contrast to traditional software development methods, agile developers liaise continuously with business clients, aiming to deliver working software as frequently as every two weeks during a project, and welcome changes to the requirement in response to evolving business needs
What are the challenges in Agile Automation Testing
Agile automation challanges
Recently, when I wanted to start my new Automated Testing Project with four resources, I thought of applying any one of the Agile methodologies. But I was not able to continue because, a series of questions were raised inside my mind. The questions are like “Is it possible to use Agile methodologies in Automated Testing?”, “Can I use traditional tools”, “Should I have to go for open-source tools”, “What are the challenges I have to face if I am implementing automation in Agile Environment”. Automated testing in the Agile environment stands a risk of becoming chaotic, unstructured and uncontrolled.
Recently, when I wanted to start my new Automated Testing Project with four resources, I thought of applying any one of the Agile methodologies. But I was not able to continue because, a series of questions were raised inside my mind. The questions are like “Is it possible to use Agile methodologies in Automated Testing?”, “Can I use traditional tools”, “Should I have to go for open-source tools”, “What are the challenges I have to face if I am implementing automation in Agile Environment”. Automated testing in the Agile environment stands a risk of becoming chaotic, unstructured and uncontrolled.
Subscribe to:
Posts (Atom)
