Fichas
Flashcards
Fichas del conjunto (23)
- 1Smoke Testing1. Are the main features working or not?
2. Smoke testing catches high-level functional errors of an app without getting into the nitty gritty
3. Smoke test suites can be created and automated or it can be both manual and automated - 2Functional TestingFunctional testing is used to verify that the software is producing the output desired by the end user.
Usability is checked - 3Regression Testing1. Retesting to check if new problems popped up as a result of software changes and updates.
2. Before making changes to a software, a program is tested then it is retested after the change
3. Essential for LARGE software applications and usually done through automation. - 4Black Box Testing1. NO programming knowledge is required.
2. It's simple testing for high-level designs and complex apps
Ex. Search engine with tester entering words in web browser search bar to retrieve results. - 5White Box Testing1. SKILLED tester is needed with coding or programming knowledge
2. validates internal framework, objects, and components of a software app.
3. Test cases are reusable
4. High costs and time consuming but removes unnecessary code and locates hidden errors during early stages of app development - 6Ad-Hoc Testing1. Random testing
2. No documents needed
3. Error guessing/exploratory testing
4. Has no structure for testing and it is criticized because it's hard to replicate an error if found.
5. However, at least important defects can still be found - 7User Acceptance Testing (UAT)Last phase of the software testing process
Actual end users test the software to make sure it's performing real world tasks in different scenarios according to specifications made.
It's also known as BETA testing. Final and critical procedure - 8Integration TestingMultiple tests together in a MODULE
Testing methodology used to test individual software components or UNITS of code to verify the interaction between DIFFERENT UNITS are interface defect free - 9Monkey TestingRandom Testing
Input data is generated randomly to check the behavior of an application
Testers even try to crash the application on purpose
No rules and works on a testers gut feelings - 10Gray Box TestingCombination of white and black box testing
Testers are not required to know programming languages or methods for testing the apps
It is not efficient because testers knowledge is limited - 11Back End TestingAny kind of database testing
Server/database testing
Data entered through the front end will go to the back end where database storage is and the database can be SQL, ORACLE,
data will be organized in tables used to support the content of the page
example: bank letting you log in to make a transfer and the results being updated and recorded permanently - 12Load Testingtests the stress load and endurance of an application
Specifically tests time frame and how many errors occur in that time
What's the peak load this software or app can handle?
Used to examine the behavior of a system under both extreme and normal conditions
RELIABILITY of the system is tested.
Ex. Shopping cart of a website is tested to see just how many items can be added and bought at a time - 13Performance TestingHow responsive and how fast is a website or server responding?
Tests if the system crashes or runs slow
Just because a system can handle smaller amounts of data does not mean it will work efficiently when subjected to peak data loads - 14Manual TestingManually testing software for defects
A tester plays the role of an end user and uses the features of an app or software to ensure it meets requirements and the correct behavior - 15Automation TestingAutomated testing where special software tools are used to control the execution of tests
These tools compare actual test results with predicted or expected results
Used when additional testing is needed and may be too difficult to perform manually
Ensures all bugs are taken care of so that the product is working as close to the target performance as possible. - 16Beta TestingBeta is pre-releasing a product to groups of people so they can test out the product
The beta version is the closest to the final released product but glitches, bugs, and issues can still be discovered and help address before an official release - 17Alpha TestingAlpha testing is not an official release of the product but has been opened up for feedback
A test to find bugs that weren't found through other tests
The goal of this testing is to refine the product by finding and fixing bugs that weren't discovered through previous tests - 18Sanity TestingPerformed under regression testing when there is NOT ENOUGH TIME for testing.
Is it worth more testing?
Does surface level testing and when a development team needs to know what the state of the product is quickly after it changes
It is done after retesting and verifies NEW functionality and bug fixes in the build. - 19Unit TestingQA does not do unit testing - Developers do
It is usually automated but can be done manually
Small parts of an app are called units and they are INDIVIDUALLY tested for proper operation - 20ALM - Application Lifecycle ManagementALM is a test management tool
It is web based
supports high level of communication among stakeholders
It can create reports and graphs for analysis purposes
Track requirements and test plans
Complete test mgmt tool - 21Test PlanTo store test scripts and design the test cases
- 22Test CaseSet of conditions or variables under which a tester will determine whether a system under test satisfies requirement or works correctly
Related requirements
Prerequisties
Test Suites ID TEst Case ID
TEst case summary - 23—
Información
- Descripción
- Fichas sobre Flashcards, creado por Sheela Kaur Chou el 16/07/2016.
- Creado por
- Sheela Kaur Chou
- Visitas
- 1
- Valoración