Scenario Based Software Testing Interview Questions And Answers For Experienced
Table of Contents
In this article we are goinf to see some of the most asked Scenario Based Software Testing Interview Questions And Answers For Experienced and freshers candidates. these questions we are collected from our group members which they faced in their interviews.
How will you test customer registration webpage?
First clarify the requirements from interviewer and then start answering
How many fields on page
Which API (SOAP/REST etc.)
Which DB is used
Which business rules for registrations
How will you approach testing any user story in Agile project?
Understand the story
Define high level scenarios what you are going to test
Elaborate those scenarios into test cases
How will you overcome the challenge of having limited/inaccurate documentation for testing?
Try to find out any related document available
Talk to project members and SMEs to understand the application
Document high level functionalities based on your discussions
Apply exploratory testing technique
Why is regression testing in Agile Development Challenging and how will you handle it?
New features added and defect fixes every sprint
Follow risk based approach to testing
Try to automate regression test suite
When in the SDLC should QA begin thinking about how to test a brand new feature?
It used to be that QA only needed to participate in certain phases of the software development life cycle (SDLC), but times have changed and many QA team members now aid in the design of the applications they test.
What are the test scenarios for the ATM machine?
Complete List of the Test Scenarios of ATM Machine. Test Scenarios For Website Testing.
1. Verify the slot for ATM Card insertion is as per the specification
2. Verify that user is presented with options when card is inserted from proper side
3. Verify that no option to continue and enter credentials is displayed to user when card is inserted correctly
4. Verify that font of the text displayed in ATM screen is as per the specifications
5. Verify that touch of the ATM screen is smooth and operational
6. Verify that user is presented with option to choose language for further operations
7. Verify that user asked to enter pin number before displaying any card/bank account detail
8. Verify that there are limited number of attempts up to which user is allowed to enter pin code
9. Verify that if total number of incorrect pin attempts gets surpassed then user is not allowed to continue further- operations like blocking of card etc. gets initiated
10. Verify that pin is encrypted and when entered
11. Verify that user is presented with different account type options like- saving, current etc.
12. Verify that user is allowed to get account details like available balance
13. Verify that user same amount of money gets dispatched as entered by user for cash withdrawal
14. Verify that user is only allowed to enter amount in multiples of denominations as per the specifications
15. Verify that user is prompted to enter the amount again in case amount entered is not as per the specification and proper message should be displayed for the same
16. Verify that user cannot fetch more amount than the total available balance
17. Verify that user is provided the option to print the transaction/enquiry
18. Verify that user user’s session timeout is maintained and is as per the specifications
19. Verify that user is not allowed to exceed one transaction limit amount
20. Verify that user is not allowed to exceed one-day transaction limit amount
21. Verify that user is allowed to do only one transaction per pin request
22. Verify that user is not allowed to proceed with expired ATM card
23. Verify that in case ATM machine runs out of money, proper message is displayed to user
24. Verify that in case sudden electricity loss in between the operation, the transaction is marked as null and amount is not withdrawn from user’s account
What are the test scenarios for pen?
- The grip of the pen: Verify if you are able to hold the pen comfortably.
- Writing: Verify if you are able to write smoothly.
- Verify that the pen is not making any sound while writing.
- Verify the ink flow. It should not overflow nor get a break either.
- Verify the quality of the material used for the pen.
- Verify if the company or pen name is visible clearly.
- Verify if the pen color or text written on the pen is not getting removed easily.
- Verify, whether the width of the line drawn by the pen is as per the expectations or not.
- Verify the ink color, it should be consistent from the start till the end.
- Verify if a pen can write on a variety of papers like smooth, rough, thick, thin, glossy etc.
- Verify for the waterproof ink. [Not for gel and ink pens].
- Verify if the ink will not get dried easily by keeping the pen open for some time. [Not for ink pen]
- Verify if any other refill fits in the pen or not.
- Verify that the pen doesn’t have sharp edges or corners.
- Verify if the ink and external assembly of the pen is made of non-toxic material.
Also, Read Getting Started with Test Automation
What are the test scenarios of lift?
- Verify the height, width, and life volume per the requirement.
- Verify that buttons for the closing lift, opening lift, fan, emergency, and all floor numbers should be there on the button panel
- Verify the presence of a display where the floor number appears
- Verify floor number is being announced on each floor
- Verify the light and aroma, along with some instrumental music
- Verify that the maximum number of people and weight is written on the wall and verify all emergency instructions.
- Verify the up and down buttons outside the life
- Verify the presence of the sensor
- Verify power used in operation since this is not the main concern here, so I am just leaving this part.
- Verify that the lift can move up and down
- Verify that the lift is capable of stopping on floors that are pressed on the button panel
- Verify that the lift closes when the close button is placed or should close once after a few times as per the manual time
- Verify that the fan is working by pressing the respective button
- Verify the sensor
- When the lift is going to close, someone has just put any object or body parts between the lift doors.
- Verify the maximum weighing capacity of life by putting the weight
- Verify that when the weight exceeds from standard, then it should give some alert message or some alert sound should ring
- Verify that the light and fan are running at power failure
- Verify the jerk on power failure
- Verify the speed of the lift. It shouldn’t be fast.
- Verify that the elevator stops on the right floor, i.e., if users click on the 2nd floor, then lifts should stop on the 2nd floor, not on the 4th floor.
- Verify the landing speed of the lift
- Verify the time between two successive floors.
- Verify that lift doors can’t be opened when the lift is moving down or upward
- Verify that lift doors are closed when no one is using it
- Verify that once the lift has crossed the specific floor and some person has to click to open the elevator, the lift should begin when the lift comes down.
Some test cases that are based on Reliability:
- Verify the working of the lift on power failure
- Verify the working of the lift once the power comes
- Verify the working of the lift once the weight exceeds the standard weight.
How do you write a test scenario for CAPTCHA?
- Check if the captcha is available on the web page.
- Check the alignment of the captcha on the web page.
- Check how much time it takes to load the captcha on a webpage.
- Check on reloading the page. A new captcha should be displayed.
- Check the alignment of the captcha.
- Check on the presence of ad blockers the captcha is displaying or not.
- Check captcha is working on adblocker or not.
- Check webpage accepts the valid captcha or not.
- Check whether a user can request a new captcha without the page loading option being present.
- Check whether an audio option is added for the captcha per the requirements.
- Check new captcha is generated in case the user adds the wrong captcha.
- Check an error message shown when the page timeout for the captcha.
- Check an error message that should be shown in case the captcha is not filled in by the user.
- Check a proper error message is shown in case the user has not filled in the captcha correctly.
- Check if an error message is shown in case the user partly fills the captcha.
- Check user IP is blocked on attempting an invalid captcha after the defined number of attempts.
- Check that the Application should accept only Valid Captcha.
- Check that the Captcha code on the screen is visible to the user.
- Check that the Captcha code format(Captch should be in Image).
- Check that the Captcha code is reusable or Not.
- Check whether the Captcha code generates new code once the page is refreshed.
- Check whether or not the Captcha code generates a new code once the user enters the wrong Captcha.
- Check that the copy-paste for the Captcha code should be hidden.
- Check that the Captcha code should be Case Sensitivity. (Upper cases and lower case).
- Check that the Captcha code should not disrupt the other fields in the form once entered wrong.
- Check that the Application should display an alert message when the user enters the wrong Captcha code.
- Check the audio version of Captcha (as per SRS).
- Check that the Captcha code should not confusing. For (Zero and O )(numbers 6 and 9).
- Check that the application should not accept the partial Captcha code as valid.
- Check only the first and the last letter from the Captcha Code
- Check By Entering the correct Captcha code, followed by a random character.
- Generic Test Cases for Captcha Functionality
- Check the Captcha is rendered in its entirety (check functionality and ideal for UI Testing)
- Check that refreshing the screen generates a random Captcha
Test Scenarios for Video Call
- Video playback: Verify that the video playback functionality is working properly without any interruptions, buffering or freezing.
- Video quality: Verify that the video quality is of the expected level according to the user’s internet speed and device specifications.
- Audio quality: Verify that the audio quality is of the expected level and is in sync with the video content.
- Video formats: Verify that the application can stream videos of different formats such as MP4, MOV, AVI, etc.
- Video resolution: Verify that the application can stream videos of different resolutions such as 360p, 480p, 720p, 1080p, etc.
- Video codecs: Verify that the application can stream videos with different codecs such as H.264, H.265, VP8, VP9, etc.
- Video streaming on different devices: Verify that the video streaming application works on different devices such as mobile phones, tablets, laptops, and smart TVs.
- Video streaming on different platforms: Verify that the video streaming application works on different platforms such as iOS, Android, Windows, macOS, and web browsers.
- Video streaming with different internet speeds: Verify that the application can stream videos with different internet speeds such as 2G, 3G, 4G, and Wi-Fi.
- Video streaming with interruptions: Verify that the application can resume video playback from the point where it was interrupted due to a lost connection, phone call, or any other interruptions.
- User experience: Verify that the video streaming application provides a good user experience with intuitive navigation, easy-to-use controls, and smooth transitions.
- System performance: Verify that the video streaming application does not consume too much battery, memory, or CPU usage and does not cause system crashes or other performance issues.
- Accessibility: Verify that the video streaming application provides accessibility features such as closed captions, audio descriptions, and other assistive technologies.
- Security: Verify that the video streaming application has proper security measures to protect user data, video content, and other sensitive information.