A Mobile Application Testing Community
Q1. Different between error, bug, defect, fault, failure?
Error: Errors are basically the deviation from the requirement, caught by testers and caused by misunderstanding of the Developers. Other words u can say coding problem or problem caused due to wrong coding practice.
Bug: If the Error found by testers are accepted as error by Developers. Then the error will called Bug. Either it should be functional or load.
Defect: Suppose any product/software is currently running as a beta version in the market/client side. Any issue currently caught in that application that are deviating the actual result from the requirement, will take as Defect.
Fault: When the product/software successfully launched in the market and running properly but due to any reason if it works unexpectedly is called Fault.
Failure: If the product fails to full fill the requirement, then it is called Failure.
Validation: Better known as testing and the process includes: System testing System Integration testing Sub System Integration testing. Unit testing. Black box testing will be used in the validate...
Verification:-conducting reviews on documents like BRS, SRS, HLDS, and LLDS......called as Verification Validation:-executing the test cases and observing whether actual result is equal to expected result...
Q3. Explain Software test lifecycle?
STLC basically contains of five stages : 1) Planning and control 2) Analysis and Design 3) Implementation and Execution 4) Evaluating Exit criteria and Reporting 5) Test Closure.
In other words u can also say that Requirement gathering, test design, test plan, and Bug reporting, regression testing and closer. And explain briefly each and every step.
New, open, assigned, fixed reopen and closed.
New when tester raises the bug the status should be new.
Open if the bug is genuine the lead should change the status open
Assign Assign to the developer
Fixed Developer fixed the bug and changes the status as fixed.
Reopen after regression or retesting tester will decide bug is closed or reopen.
Closed fixed by developer and tester review and closed.
Q5. What is software Testing Methodologies?
These are some of the commonly used test methodologies:
1. Waterfall model
2. V model
3. Spiral model
4. Rational Unified Process (RUP)
5. Agile model
6. Rapid Application Development (RAD)
Explain anyone which ur current company follows..
Q6. What is traceability matrix?
Traceability matrix is a document in which we map the test cases with the requirements. In general we check whether the application works as per requirements or whether we had covered all the required functionality through test cases.
Q7. What is performance testing?
Performance testing is the testing, which is performed, to ascertain how the components of a system are performing, given a particular situation. Resource usage, scalability and reliability of the product are also validated under this testing. This testing is the subset of performance engineering, which is focused on addressing performance issues in the design and architecture of software product.
Q8. Different kind of testing performed in mobile application testing?
Functional testing – This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application.
System testing – Entire system is tested as per the requirements. Black-box type testing that is based on overall requirements specifications, covers all combined parts of a system.
Incremental integration testing – Bottom up approach for testing i.e continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately. done by programmers or by testers.
End-to-end testing – Similar to system testing, involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
Acceptance testing -Normally this type of testing is done to verify if system meets the customer specified requirements. User or customer does this testing to determine whether to accept application.
Usability testing – User-friendliness check. Application flow is tested, Can new user understand the application easily, Proper help documented whenever user stuck at any point. Basically system navigation is checked in this testing.
Install/uninstall testing - Tested for full, partial, or upgrade install/uninstall processes on different operating systems under different hardware, software environment
Compatibility testing – Testing how well software performs in a particular hardware/software/operating system/network environment and different combination s of above.
Recovery testing – Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.