ADOBE
𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧: How do you handle dynamic web tables in test automation?
Hint: Use XPath or CSS selectors to locate table rows and columns dynamically. Loop through rows and columns to interact with or verify table data.𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧: How do you find the longest palindromic substring in a given string?
Hint: Use dynamic programming or expand around the centre approach to identify the longest substring that reads the same forward and backward.
𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧: You have a lighter and two ropes. Each rope burns in 60 minutes but not evenly. How can you measure:
45 minutes?
50 minutes?
𝐀𝐧𝐬𝐰𝐞𝐫:
𝟒𝟓 𝐌𝐢𝐧𝐮𝐭𝐞𝐬: Light rope 1 at both ends and rope 2 at one end simultaneously. When rope 1 burns out (30 minutes), light the other end of rope 2 (15 minutes).
**try for 50 minutes
𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧: Given two strings s1 and s2, determine if s2 contains a permutation of s1. In other words, return true if one of s1's permutations is a substring of s2, or false otherwise.
input: s1 = "ab" s2 = "eidbaooo"
output: true
𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐀𝐩𝐩𝐫𝐨𝐚𝐜𝐡:
Understand the Problem: We need to find if any permutation of s1 is a substring of s2.
Sliding Window Technique: Use a sliding window approach to compare segments of s2 with s1.
Question : What do you understand about beta testing? What are the different types of beta testing?
Answer: Genuine users of the software application undertake beta testing in a real environment. One type of User Acceptance Testing is beta testing. A small number of end-users of the product are given a beta version of the program in order to receive input on the product quality. Beta testing reduces the chances of a product failing and improves the product's quality by allowing customers to validate it.
Following are the different types of beta testing :
Traditional Beta testing: Traditional Beta testing is distributing the product to the target market and collecting all relevant data. This information can be used to improve the product.
Public Beta Testing: The product is made available to the general public via web channels, and data can be gathered from anyone. Product improvements can be made based on customer input. Microsoft, for example, undertook the largest of all Beta Tests for its operating system Windows 8 prior to its official release.
Technical Beta Testing: A product is delivered to a group of employees of a company and feedback/data is collected from the employees.
Focused Beta Testing: A software product is distributed to the public for the purpose of gathering input on specific program features. For instance, the software's most important features.
Post-release Beta Testing: After a software product is launched to the market, data is collected in order to improve the product for future releases.
Question : What do you understand about alpha testing? What are its objectives?
Answer: Alpha testing is a type of software testing that is used to find issues before a product is released to real users or the general public. One type of user acceptability testing is alpha testing. It is referred to as alpha testing since it is done early in the software development process, near the ending. Homestead software developers or quality assurance staff frequently undertake alpha testing. It's the final level of testing before the software is released into the real world.
Following are the objectives of alpha testing:
The goal of alpha testing is to improve the software product by identifying flaws that were missed in prior tests.
The goal of alpha testing is to improve the software product by identifying and addressing flaws that were missed during prior tests.
The goal of alpha testing is to bring customers into the development process as early as possible.
Alpha testing is used to gain a better understanding of the software's reliability during the early phases of development.
Question : What do you understand about Risk based testing?
Answer: Risk-based testing (RBT) is a method of software testing that is based on risk likelihood. It entails analyzing the risk based on software complexity, business criticality, frequency of use, and probable Defect areas, among other factors. Risk-based testing prioritizes testing of software programme aspects and functions that are more important and likely to have flaws.
Risk is the occurrence of an unknown event that has a positive or negative impact on a project's measured success criteria. It could be something that happened in the past, something that is happening now, or something that will happen in the future. These unforeseen events might have an impact on a project's cost, business, technical, and quality goals.
Risks can be positive or negative. Positive risks are referred to as opportunities, and they aid in the long-term viability of a corporation. Investing in a new project, changing corporate processes, and developing new products are just a few examples.
Negative risks are also known as threats, and strategies to reduce or eliminate them are necessary for project success.
Question : Differentiate between walkthrough and inspection.
Answer:
Walkthrough - A walkthrough is a technique for doing a quick group or individual review. In a walkthrough, the author describes and explains his work product to his peers or supervisor in an informal gathering to receive comments. The legitimacy of the suggested work product solution is checked here. It is less expensive to make adjustments while the design is still on paper rather than during conversion. A walkthrough is a form of quality assurance that is done in a static manner.
Walkthrough vs Inspection
It is informal in nature.
It is formal in nature.
The developer starts it.
The project team starts it.
The developer of the product takes the lead throughout the walkthrough.
The inspection is conducted by a group of people from several departments. The tour is usually attended by members of the same project team.
The walkthrough does not employ a checklist.
A checklist is used to identify flaws.
Overview, little or no preparation, little or no preparation examination (real walkthrough meeting), rework, and follow up are all part of the walkthrough process.
Overview, preparation, inspection, rework, and follow-up are all part of the inspection process.
In the steps, there is no set protocol.
Each phase has a formalized protocol.
Because there is no specific checklist to evaluate the programme, the walkthrough takes less time.
An inspection takes longer since the checklist items are checked off one by one.
It is generally unplanned in nature.
Scheduled meeting with fixed duties allocated to all participants.
Because it is unmoderated, there is no moderator.
The responsibility of the moderator is to ensure that the talks stay on track.
reference - https://www.interviewbit.com/sdet-interview-questions/#walkthrough-vs-inspection -- to be deleted
Question : What do you understand about fuzz testing? What are the types of bugs detected by fuzz testing?
Answer: Fuzz Testing is a software testing technique that utilizes erroneous, unexpected, or random data as input and then looks for exceptions like crashes and memory leaks. It's a type of automated testing that's used to define system testing techniques that use a randomized or dispersed approach. During fuzz testing, a system or software program may have a variety of data input problems or glitches.
Following are the different phases of Fuzz Testing:
Question :
Answer:
Question :
Answer:
Question :
Answer:
