What is the difference between a bug and an error?
What is the difference between a bug and an error?
Error is a mistake or misunderstanding on the part of software developer. Bugs is a also called defect or fault, which is introduced into the software as a result of error. It is an anamoly in the software that may cause it to behave incorrectly and not according to its specifications.
What is the most common type of bug in software?
The most common software bugs
- Crash.
- Functional error.
- For example, the functionality of a ‘Cancel’ button is that the window should be closed and none of the changes should be saved.
- Typos.
- Missing command.
- Calculation error.
- Hardware usage error.
What are the QA processes?
QA process
- Review of requirements.
- Test planning / writing test cases.
- Unit testing.
- Integration testing.
- System testing.
- Performance testing.
- Security testing.
- Cross-browser testing / cross-platform testing.
What is difference between monkey testing and gorilla testing?
Monkey testing is a type of random testing and no test cases used in this testing. Gorilla Testing is a manual testing and it is repetitively performed
Who performs usability testing?
Usability testing is a popular UX research methodology. In a usability-testing session, a researcher (called a “facilitator” or a “moderator”) asks a participant to perform tasks, usually using one or more specific user interfaces
Can you explain usability testing?
Usability testing refers to evaluating a product or service by testing it with representative users. Typically, during a test, participants will try to complete typical tasks while observers watch, listen and takes notes.
What are the three main principles of usability testing?
Three basic principles underlie usability testing:
- Usability testing permeates product development.
- Usability testing involves studying real users as they use the product.
- Usability testing involves setting measurable goals and determining whether the product meets them.
How do you write a load test?
In summary, forming an action plan for load testing is quite simple:
- Record user activity for different use cases.
- Throw traffic at the application for different scenarios.
- Reproduce performance related issues (if any).
- Identify bottlenecks in the application.
- Fix the performance problems.
How do you plan a performance test?
5 Ways to Plan Application Performance Testing
- Build a Complete Test Strategy. Start with a detailed test strategy to determine the types of tests that you need to perform to perfect the application.
- Try to Include Think Time in Testing.
- Identify the Performance Bottleneck.
- Learn from Earlier Experiences.
- Emphasize on Baseline Tests.