Thananjayan Rajasekaran

You don’t trust your QA or SDET if… 1. You skip their feedback in sprint reviews 🗣️ If QA raises concerns during sprint reviews or retrospectives and they’re brushed aside, it might indicate a lack of trust in their perspective. Their job is to identify risks before they become costly problems. 2. You don’t involve them early in the development cycle 🛠️ Leaving QA out of requirements gathering or design discussions signals you don’t see them as key stakeholders. Involving them early ensures they understand the context and can prepare better test strategies. 3. You question every bug they find 🐞 If you spend more time debating the validity of a reported issue than addressing it, it can create friction and discourage thorough testing. Trust their expertise—they're advocating for your product’s success. 4. You don’t empower them with the right tools 🛠️ Automation requires resources. If your SDET is asking for tools or infrastructure upgrades and you're hesitating, it could indicate a lack of trust in their ability to deliver results. 5. You view testing as a bottleneck ⏳ The mindset that QA is “slowing things down” often stems from undervaluing the critical role they play. Testing isn’t a delay—it’s an investment in your product’s quality and user satisfaction. 6. You assume developers should handle everything 👩‍💻👨‍💻 Developers and testers have distinct roles. Assuming developers can “test their own code” is not only unrealistic but also undermines the value of having a dedicated QA team. 7. You skip retrospectives on escaped bugs 🔄 When bugs reach production, it’s not just QA’s responsibility—it’s the entire team’s. Skipping a retrospective or blaming QA shows a lack of trust in their problem-solving ability. Why trust matters 🔑 Trust between developers, testers, and product teams fosters collaboration and innovation. A trusted QA team doesn’t just find bugs—they enhance quality, protect your reputation, and ensure smooth user experiences. Trust is built through inclusion, communication, and acknowledgment of their expertise. What’s your experience? Have you seen these trust issues in action—or overcome them? Let’s discuss in the comments!

1

1 Comment

Interview questions for SDET roles, Part-2 (Round 2) A Top FinTech Company Experience - 3-8 years Questions - 1) Introduce yourself 2) Explain the complete Scrum process followed in your Project 3) How Estimations were given for a Story and How do you suggest Test Estimations? 4) Give an example of Low priority & Low severity, Low Priority & High Severity (please don’t give examples commonly mentioned in blogs or YouTube videos). Give some unique examples. 5) There is a date picker which has a start date and end date, and once you select both dates, now these 2 dates get displayed in another 2 web pages. Once you modify they get modified in these 2 webpages. Derive as many scenarios as possible for this case. 6) What exactly is Smoke and Sanity Testing (Give some good examples from your project) 7) In what cases you performed smoke, regression, Sanity, Retesting and End to End testing in your Project, explain in detail. 8) How do you handle radio buttons 9) What is implicit wait, have you implemented it in your project? 10) Explain with examples where implicit and explicit waits can be used. Do you implement them together? 11) Have you designed the Automation framework from scratch? 12) Why you have implemented By Approach in your Page classes and why not Page Factory approach 13) What happens when duplicate values are added in HashMap? 14) Are you Ready to work from 1:30 PM to 11PM IST Timings? 15) How do you make sure Abstraction is maximised in your Tests? 16) Handling mail while working in Automation, explain with writing code 17) How do you implement builder pattern using LomBok? 18) Git Branching approach in detail 19) How to keep API Tests idempotent? 20) How Regression Suites are handled in your Automation Project? 21) Is it possible to integrate API generated cookies directly with Selenium WebDriver tests? If yes how? 22) Explain the Test Stack Implemented in your project Coding Problems: 1) Given an integer array nums sorted in non-decreasing order, remove the duplicates in-place such that each unique element appears only once. The relative order of the elements should be kept the same Example: Input: nums = [0,0,1,1,1,2,2,3,3,4] Output: 5, nums = [0,1,2,3,4,_,_,_,_,_] Explanation: Your function should return k = 5, with the first five elements of nums being 0, 1, 2, 3, and 4 respectively. 2) Find the largest, second largest, smallest and second smallest numbers in the given array. -x-x- You can find the answers for all above questions in my latest updated Q&A bank for SDETs (paid): https://lnkd.in/gSU-m2F7 Top 5 skills to get a CTC of 20 LPA, skills covered in my latest youtube video: https://lnkd.in/gguVEaSM #japneetsachdeva

181

17 Comments

🚀JavaScript series For SDET's: Chapter1❤️ What is the setup required to start working on JavaScript? ✅ Browser Setup: - Install a Browser[ex: chrome], go to Developer tools > Sources Tab > Snippets. - Add a new snippet & start writing your JavaScript code - You can run it or debug it. - This is only helpful if you are planning to practice & learn JavaScript code. - You can't use it to create a project. - Also the JS Engine provided by browser will not suffice to your need of Automation scripts as you would want to use capabilities which are meant for a machine & not just a browser. - It would be a good playground for Developers, but for SDET's recommendation is the Node js setup. ✅ Node JS Setup. - Node JS is your JavaScript engine for Desktop machines. - If you want to run or create JavaScript code, you can't do it without installing node.js environment. - Download & Install Node Js - You will also need an editor to write your code, my recommendation is to install VSCode. - Now you can open VSCode & create a Directory on your machine & start creating files with extensions as 'js' - Now you are ready to work on JavaScript code. Follow me for upcoming chapters on this series. Plan is to share a new chapter every day. Let's become better every day & learn the things as they should be learnt without any sugar coating. ------------------------------------------- If you are struggling with JavaScript, TypeScript, NodeJS in your current job or wants to upskill yourself. You can join our below course & become part of family of 3000+ SDET students. ✅JavaScript - TypeScript Program [Including DSA stack + Devops Stack]: Original Price: 3,999/- JavaScript, TypeScript, NodeJS, NPM, Searching Algorithm, Sorting Algorithm, Data Structures, Git, GitHub, Devops Basics [Linux, Docker, AWS, Jenkins], Web Automation [HTML, CSS , DOM, etc..] 🌟 1 Day Free Trial Period Offer: - To help you decide & bring transparency in the content covered. - I am offering 24 hour Free Trial period access to all our modules. During this time, you don't need to pay me anything, if satisfied with the content only then initiate the payment. ✅ 25% discount offer. During the 24 hour trial period, if you decide to join us. Revert back to us within those 24 hours & we will extend 25% discount on the price. Original Price: 3,999/- | Discounted Price: Rs 2,999/- 👉 Benefits: Access to Recording videos for 3 years. Access to multiple GitHub Repositories where code is maintained day wise for all the modules. Access to our Discord community to help with your queries. ✍ How to get Enrolled? - Use the link in the comment section to Register yourself. [No payment required at this stage.] - Once you register, will grant you access to our modules for free for 24 hour trial period. - Within these 24 hours, If you feel satisfied with the content, you can initiate the payment & get enrolled & take benefit of these discounted prices. Happy Learning! 🙂 👉Follow me for daily learning posts.

12

2 Comments

What kind of APIs can you explore & understand before getting into SDET interviews? 1) Web APIs: These are used to enable communication between web servers and clients. For instance, the Twitter API allows developers to access and interact with Twitter's features, such as retrieving tweets or posting new ones. 2) Operating System APIs: These provide an interface for applications to interact with the underlying operating system. The Windows API, for instance, allows software to access various functionalities of the Windows operating system, like creating windows, managing files, and controlling hardware devices 3) Database APIs: These allow applications to communicate with databases. The Java Database Connectivity (JDBC) API enables Java applications to interact with various databases using a standardized interface. 4) Library APIs: Programming libraries often come with APIs that provide predefined functions and classes. The Python Standard Library, for example, offers various modules with APIs for tasks like file handling, networking, and data manipulation. 5) Remote APIs: These enable remote control of devices or services. The remote API of a smart home system might allow a mobile app to control lights, thermostats, and security cameras from a distance. 6)Third-Party APIs: Many companies offer APIs to allow developers to integrate their services into other applications. The Google Maps API lets developers embed interactive maps into their websites or apps. -x-x- Learn & Use GEN AI, API Testing, Automation & more using an updated course for SDETs: https://lnkd.in/gusymgFi Test Automation Engineer Quiz, Exp: 3 to 8 yrs: https://lnkd.in/gHTH3K_g #japneetsachdeva

78

2 Comments

Top 8 Types of API Tests every SDET should know! 1) Smoke Tests: Validating bare minimum crucial API calls are working for applications. ↳ Tools: Postman, Swagger, Manual Tests 2) Functional Tests: Validating each API for its prominent functionality. Like Post requests for data creation and validating in Database whether data sent is created in the right table, structure etc. ↳ Tools: RestAssured, Locust, Gatling, Requests, Postman with manual Db validation etc. 3) Integration Tests: Validating multiple requests in sync like calling Post rqst and then Get rqst to validate whether data is created or not. ↳ Tools: Postman, Requests, RestAssured, Locust etc. 4) Load Tests: Validating the load capacity of APIs. This is crucial when user footfall increases. ↳ Tools: JMeter, LoadRunner, Locust, Gatling etc. 5) Stress Tests: Breaking the APIs. This helps to know about the threshold. ↳ Tools: JMeter, LoadRunner, Locust, Gatling etc. 6) Security Testing: Validating external threats if any for APIs. ↳ Tools: Pynt, OWASP top 10 vulnerabilities with BurpSuite etc. 7) Fuzz Tests: Validating APIs and servers with sending unexpected data and validate the response received. ↳ Tools: Postman, Requests, RestAssured etc. 8) Regression Tests: Validating new changes made in application or APIs should not break existing functionality. ↳ Tools: Postman, Requests, RestAssured etc. Keep the hustle on, Guys !!! Stay tuned for more !!! Join my WhatsApp Channel:- https://lnkd.in/dYMtyi_K Follow Tushar Desai for more insightful content. Credit:- Waqar Mahmood

37

2 Comments

POLL 📣 How would you rank your team in terms of automated testing maturity? 🤔 Comment below!

4

Top API Terms that every SDET should know before starting with Interviews ❓ What is Rest API? REST API, or Representational State Transfer, is a design approach that operates on a client-server model where client apps initiate a request to view or edit server info. Each request to a RESTful API is autonomous. This means that every request needs to have all the requisite info for the server to grasp and address that request. Resources are the underlying content presented by the API, which are distinguished by their URIs, or Uniform Resource Identifiers. Standard HTTP modes are the primary method of doing operations on resources in RESTful APIs: - GET, which retrieves data - POST, which makes new data - PUT, to adjust current data and DELETE, getting rid of the data. Data entities are typically illustrated in two accessible formats, JSON or JavaScript Object Notation, and XML, the extensible Markup Language. The required data to manage the client's installment has to be available in each appeal from the client to the server. In-between requests, the server does not sustain any status from the clients. The uniform interface is a key feature of REST API, that simplifies the connection between client and server. Therefore it makes concerted use of standard HTTP modes, resources URIs along with their response calendars. ⭐ Note: Refer below PDF before interviews just to refresh all the important terms used frequently by SDETs or SDEs. During Testing or Development. -x-x- Get complete Interview Prep material for SDETs here (paid): https://lnkd.in/gSU-m2F7 Full Stack QA and Test Architect Prep Material available here (paid): https://lnkd.in/dWjpT3-3 #japneetsachdeva

68

2 Comments

Top API Terms that every SDET should know before starting with Interviews ↳ What is Rest API? REST API, or Representational State Transfer, is a design approach that operates on a client-server model where client apps initiate a request to view or edit server info. Each request to a RESTful API is autonomous. This means that every request needs to have all the requisite info for the server to grasp and address that request. Resources are the underlying content presented by the API, which are distinguished by their URIs, or Uniform Resource Identifiers. ↳ Standard HTTP modes are the primary method of doing operations on resources in RESTful APIs: - GET, which retrieves data - POST, which makes new data - PUT, to adjust current data and DELETE, getting rid of the data. ↳ Data entities are typically illustrated in two accessible formats, JSON or JavaScript Object Notation, and XML, the extensible Markup Language. The required data to manage the client's instalment has to be available in each appeal from the client to the server. In-between requests, the server does not sustain any status from the clients. The uniform interface is a key feature of REST API, that simplifies the connection between client and server. Therefore it makes concerted use of standard HTTP modes, resources URIs along with their response calendars. ↳ Note: Refer below PDF before interviews just to refresh all the important terms used frequently by SDETs or SDEs. During Testing or Development. -x-x- Get complete Interview Prep material for SDETs here (paid): https://lnkd.in/gSU-m2F7 Full Stack QA and Test Architect Prep Material available here (paid): https://lnkd.in/dWjpT3-3 #japneetsachdeva

82

What's lacking in every QA and SDET that I have interviewed in 2024? . . Not having a QA mindset! Every QA now just wants to work in automation, but why? Do you think developing test automation frameworks will improve your skill? OR having created automation will help you step up the ladder of salary and designation more quickly? No, it doesn't work like this! After interviewing so many candidates I can clearly say, You don't know how to create a Test Strategy, Test Scenarios, Proper Test coverage, Not able to evaluate a system as a End-User, No basic knowledge of concepts like when and where to implement automation? etc. If you are going to give an interviews just by doing "rattafication" then you will not be able to progress your career. QA is not automation only! Also specifically mentioning, showing unwillingness to test the system during development phase and only to work in automation can make you rejected in lots interviews. Lot's of product based organization primarily focus on Shift left manual testing and they don't care about automation. Learning trending technologies is useful but shifting your focus from importance of Quality is going to hamper your growth. Every aspect of Software is judged by its Quality. If you cannot improve it quality then Learning Automation is not going to lead you anywhere. I have seen QA's earning more then 85 LPA INR that too in India. There definitely will be people having much better salaries too. So improve your skills even though its Manual QA. Both are equally important :) Follow for more: Japneet Sachdeva -x-x- Learn and use lots of QA, Automation, API, Docker, SQL, Maven, CI_CD and many more complete questions with answers (paid): https://lnkd.in/gSU-m2F7 Crack Test Automation Interviews using JAVA, Master Package for Clearing QA Automation Interviews: https://lnkd.in/g5hr9bea #japneetsachdeva #falsehopes #sdet

274

13 Comments

What's lacking in every QA and SDET that I have interviewed in 2024? . Not having a QA mindset! Every QA now just wants to work in automation, but why? Do you think developing test automation frameworks will improve your skill? OR having created automation will help you step up the ladder of salary and designation more quickly? No, it doesn't work like this! After interviewing so many candidates I can clearly say, You don't know how to create a Test Strategy, Test Scenarios, Proper Test coverage, Not able to evaluate a system as a End-User, No basic knowledge of concepts like when and where to implement automation? etc. If you are going to give an interviews just by doing "rattafication" then you will not be able to progress your career. QA is not automation only! Also specifically mentioning, showing unwillingness to test the system during development phase and only to work in automation can make you rejected in lots interviews. Lot's of product based organization primarily focus on Shift left manual testing and they don't care about automation. Learning trending technologies is useful but shifting your focus from importance of Quality is going to hamper your growth. Every aspect of Software is judged by its Quality. If you cannot improve it quality then Learning Automation is not going to lead you anywhere. I have seen QA's earning more then 85 LPA INR that too in India. There definitely will be people having much better salaries too. So improve your skills even though its Manual QA. Both are equally important :) Follow for more: Japneet Sachdeva -x-x- Learn and use lots of QA, Automation, API, Docker, SQL, Maven, CI_CD and many more complete questions with answers (paid): https://lnkd.in/gSU-m2F7 Crack Test Automation Interviews using JAVA, Master Package for Clearing QA Automation Interviews (paid): https://lnkd.in/g5hr9bea #japneetsachdeva #falsehopes #sdet

151

5 Comments

🚀 Can You Pass This Automation Testing Mock Interview in Just 40 Minutes? | For Experienced SDET 🔍 Are you an experienced SDET or Automation Tester preparing for your next big interview? 🤔 🎥 I’ve just uploaded a Mock Interview that covers real, challenging questions you’ll face in today’s job market! Test your skills, sharpen your responses, and see if you can pass in just 40 minutes. ⏱️ 👉 Watch Now and get valuable insights to ace your next interview! 📌 Video includes: Advanced Automation Testing scenarios Key questions for SDET roles Tips and tricks for nailing the technical interview 🔗 https://lnkd.in/gP2_9MB7 #AutomationTesting #SDET #MockInterview #QAInterview #SoftwareTesting #AutomationEngineer #TechInterview #InterviewPreparation #JobInterviewTips #CareerGrowth

20

4 Comments

Maven and Gradle interview questions and answers -------------------------------------------------- 1. What is the purpose of build tools like Maven and Gradle? Maven and Gradle are project build tools. It helps in managing dependency and their versions (we can add/modify dependencies), run the test and helps in package to WAR /JAR files. To deploy to the test / production environment. -------------------------------------------------- 2. What are the different phases of Maven build lifecycle? - Validate -> checks if project is correctly configured - compile -> compile the source code - Test -> runs the unit test (using testing framework like JUnit, TestNG) - package -> packages compiled code into distributed format - Integration test -> run integration test - verify -> verify everything is ok - install ->install packaged application to local maven repository - deploy -> deploy application to remote repository -------------------------------------------------- 3. How do you handle dependencies in Maven/Gradle? In Maven you can handle dependencies using pom.xml file. In Gradle it can be done using build. gradle -------------------------------------------------- 4. What are the benefits of using Maven/Gradle for project management? 1. It supports dependency management 2. Helps in making a standardized project structure which is easy to understand and maintain 3. Build automation 4. Plugin support for compiling code, generate reports etc 5. Consistent builds across different environments 6. Integrates with CI/CD tools -------------------------------------------------- 5. How do create and manage plugins in Maven/Gradle? Plugins are configured in Maven under <plugins> section in pom.xml file. For Gradle, plugins are managed plugins block in build.gradle file plugins { id 'java' } #testing #QA #Maven #Gradle #interview

1

Why does every Software Tester need to learn Design Patterns for Automation Testing?!? **** "Do you know the moment when you feel that your code remained like Tahrir Square when the employees left like that😂?" Modifications here, Fix there, and in the end you remain like the one who runs behind the trailer! Here is the intervention of Design Patterns that tells you: "Wait a minute, why are you so complicated in your life? Let's get your code organized, scalable, and without noise or heartache!" ..... Medicine means what Design Patterns in short? Simply put, these are ready-made solutions to problems that we encounter a lot and we write code. Instead of inventing atoms every time, you use the patterns that people have tried and made sure are the best way to solve the problem. *** Well, what are the design patterns you can see, such as" life key" for Testers? 1️⃣First: Page Object Model (POM): Imagine that you are a script worker who adds a product. Instead of writing Locators and Action Faces Test, you separate them into Class on their own. The code remains Modular. If there is a change in the add product page, all you have to do is modify one class not the whole test. Like you separate the electrician's work from the work of the debater, everyone works in his field. --- 2️⃣ Second: Factory Pattern: You have a project and you want to run it on more than one Browser, for example (Chrome, Firefox, etc.). Instead of writing code for each browser, Class is responsible for choosing the right WebDriver. Instead of sitting down, you add If-Else at every time, leaving everything clustered in one place. Like when someone is responsible for organizing a queue, instead of everyone crowding himself. --- 3️⃣Third: Singleton Pattern: Do you know when you open more than one Browser at the same time and the code starts to run Crash? Singleton guarantees that you only use one Instance for WebDriver for the duration of the test. Reduce resources and avoid mistakes. For example, you work on one bus instead of each employee bringing his own car. --- 4️⃣ Third: Observer Pattern: Everything that happens during the test (like a new step or error), is automatically recorded in the logs or speaks the report. All you need is Transparent, you know exactly what happened in your test. Like the meteorological alerts that send you as soon as the rain starts to come down. --- The bottom line: If you want your framework to remain modular, organized, and scalable, you should look respectfully on the design patterns. Not only will they save time and effort, but they will also leave the code for you to degrade in the Portfolio and say: "Bass, Pasha, this is my job!" #postcredit Mohamed Tawfeek 😇

43

1 Comment

Have you worked on Selenium & PlayWright? Most famous interview questions for Automation interview. Selenium Exceptions vs Playwright Exceptions 🔥 ➡ Selenium Exceptions <> NoSuchElementException: Occurs when an element is not found using a locator strategy <> TimeoutException: Arises when a command does not complete its execution within the defined time <> StaleElementReferenceException: Happens when an element is no longer present in the DOM <> ElementNotInteractableException: Occurs when an element is present but not in a state that can receive input <> ElementNotVisibleException: Happens when an element is not visible on the screen but expected to be interacted with <> ElementClickInterceptedException: Occurs when an element is found but cannot be clicked due to another element obscuring it <> UnexpectedAlertPresentException: Arises when an unexpected alert pops up while executing a command <> InvalidSelectorException: Happens when the provided selector is invalid or incorrect <> SessionNotFoundException: Occurs when the WebDriver session is not found or has ended prematurely <> UnhandledAlertException: Happens when an alert is present, and the command used to handle it is not supported ➡ Playwright Exceptions <> TimeoutError: This occurs when an operation does not complete within the specified timeout <> SelectorError: Arises when a provided selector does not match any elements <> PageError: Represents errors related to actions or interactions with a page <> FrameError: Occurs when dealing with frames or iframes and an operation cannot be executed <> RequestFailedError: Represents failures in network requests or response handling <> RouteHandlerError: Represents errors when handling routes or intercepting network requests <> BrowserContextError: Arises when there are issues related to browser contexts, such as creating or manipulating them <> BindingCallError: Occurs when there are issues with function calls or bindings within the Playwright API <> WorkerError: Represents errors occurring within workers or threads in Playwright's execution environment Do follow for more - Japneet Sachdeva -x-x- Get access to my latest course to become a successful SDET in 2024 on Udemy: https://lnkd.in/gx8XGRVK Prepare for SDET interviews with more then 950+ interview questions and answers collected specifically for 2024: https://lnkd.in/gSU-m2F7 #japneetsachdeva

112

3 Comments

Complex QA Interview Questions for Experience Range: 3 to 8 yrs Q 1 - What are un-reproducible bugs? Ans: The following kind of bugs can be categorised as un-reproducible bugs: Defects that surface due to issues of low memory. Errors or bugs that arise due to addresses pointing to memory locations that do not exist. Race conditions are error scenarios that occur when the time of execution of one event impacts another event executing in a sequence. Q 2 - What is a critical bug? Ans: A critical bug is a bug that impacts a major functionality of the given application. This means affecting a large area of the functionality or breaking any functionality and there is no other method to overcome this problem. The application cannot be delivered to the end user unless the critical bug is fixed. Q 3 - How will you determine when to stop testing? Ans: It can be hard to know when to stop testing. Many modern software applications are so complicated and run in such a relaxed environment that thorough testing is impossible. The following are some regular criteria to consider when considering when to end testing: Deadlines are very important (release deadlines, testing deadlines, etc.) Completed test cases with a certain percentage of passing When the test budget runs out When the coverage of code, functionality, or requirements arrives at a certain point, it is said to be complete When the bug rate drops below a specific threshold When the beta or alpha testing stage is over Q 4 - What are the best software quality practices as per your work experience? Ans: These are some best practices I usually follow to deliver a high-quality product and effectively perform my QA roles and responsibilities in software testing Review the requirements in depth before you start with the development This is the time to review the code Write comprehensive test cases as required Perform session-based testing, then risk-based testing Set the priority for bugs based on usage Run a regression cycle Perform sanity tests on pre-prod Focus on QA test reports Q 5 - Describe the defect cycle steps Ans: As a candidate, you should have knowledge of the bug cycle, which typically follows these steps: Defect discovery: A defect is discovered during testing or by a customer. Defect reporting: The tester reports the defect along with a detailed description and steps to reproduce it. Defect prioritisation: The defect is prioritised based on its severity and impact on the product. Defect assignment: The defect is assigned to a developer to investigate and fix. Defect fixing: The developer fixes the defect and verifies the fix. Defect Validation: The tester validates that the defect has been fixed and closes. Defect closure: The defect is closed after being fixed and validated. Note - This is not a defect life cycle -x-x- 950+ Test Automation Interview Prep, Questions with answers and Coding questions exercises (paid): https://lnkd.in/gSU-m2F7 #japneetsachdeva

326

7 Comments

Complex QA Interview Questions for Experience Range: 3 to 8 yrs Q 1 - What are un-reproducible bugs? Ans: The following kind of bugs can be categorised as un-reproducible bugs: Defects that surface due to issues of low memory. Errors or bugs that arise due to addresses pointing to memory locations that do not exist. Race conditions are error scenarios that occur when the time of execution of one event impacts another event executing in a sequence. Q 2 - What is a critical bug? Ans: A critical bug is a bug that impacts a major functionality of the given application. This means affecting a large area of the functionality or breaking any functionality and there is no other method to overcome this problem. The application cannot be delivered to the end user unless the critical bug is fixed. Q 3 - How will you determine when to stop testing? Ans: It can be hard to know when to stop testing. Many modern software applications are so complicated and run in such a relaxed environment that thorough testing is impossible. The following are some regular criteria to consider when considering when to end testing: Deadlines are very important (release deadlines, testing deadlines, etc.) Completed test cases with a certain percentage of passing When the test budget runs out When the coverage of code, functionality, or requirements arrives at a certain point, it is said to be complete When the bug rate drops below a specific threshold When the beta or alpha testing stage is over Q 4 - What are the best software quality practices as per your work experience? Ans: These are some best practices I usually follow to deliver a high-quality product and effectively perform my QA roles and responsibilities in software testing Review the requirements in depth before you start with the development This is the time to review the code Write comprehensive test cases as required Perform session-based testing, then risk-based testing Set the priority for bugs based on usage Run a regression cycle Perform sanity tests on pre-prod Focus on QA test reports Q 5 - Describe the defect cycle steps Ans: As a candidate, you should have knowledge of the bug cycle, which typically follows these steps: Defect discovery: A defect is discovered during testing or by a customer. Defect reporting: The tester reports the defect along with a detailed description and steps to reproduce it. Defect prioritisation: The defect is prioritised based on its severity and impact on the product. Defect assignment: The defect is assigned to a developer to investigate and fix. Defect fixing: The developer fixes the defect and verifies the fix. Defect Validation: The tester validates that the defect has been fixed and closes. Defect closure: The defect is closed after being fixed and validated. Note - This is not a defect life cycle -x-x- 950+ Test Automation Interview Prep, Questions with answers and Coding questions exercises (paid): https://lnkd.in/gSU-m2F7 #japneetsachdeva

330

9 Comments

Complex QA Interview Questions for Experience Range: 3 to 8 yrs Q 1 - What are un-reproducible bugs? Ans: The following kind of bugs can be categorised as un-reproducible bugs: Defects that surface due to issues of low memory. ↳ Errors or bugs that arise due to addresses pointing to memory locations that do not exist. ↳ Race conditions are error scenarios that occur when the time of execution of one event impacts another event executing in a sequence. Q 2 - What is a critical bug? Ans: A critical bug is a bug that impacts a major functionality of the given application. This means affecting a large area of the functionality or breaking any functionality and there is no other method to overcome this problem. The application cannot be delivered to the end user unless the critical bug is fixed. Q 3 - How will you determine when to stop testing? Ans: It can be hard to know when to stop testing. Many modern software applications are so complicated and run in such a relaxed environment that thorough testing is impossible. The following are some regular criteria to consider when considering when to end testing: ↳ Deadlines are very important (release deadlines, testing deadlines, etc.) ↳ Completed test cases with a certain percentage of passing ↳ When the test budget runs out ↳ When the coverage of code, functionality, or requirements arrives at a certain point, it is said to be complete ↳ When the bug rate drops below a specific threshold ↳ When the beta or alpha testing stage is over Q 4 - What are the best software quality practices as per your work experience? Ans: These are some best practices I usually follow to deliver a high-quality product and effectively perform my QA roles and responsibilities in software testing ↳ Review the requirements in depth before you start with the development ↳ Write comprehensive test cases as required ↳ Perform session-based testing, then risk-based testing ↳ Set the priority for bugs based on usage ↳ Run a regression cycle ↳ Perform sanity tests on pre-prod ↳ Focus on QA test reports Q 5 - Describe the defect cycle steps Ans: As a candidate, you should have knowledge of the bug cycle, which typically follows these steps: ↳ Defect discovery: A defect is discovered during testing or by a customer. ↳ Defect reporting: The tester reports the defect along with a detailed description and steps to reproduce it. ↳ Defect prioritisation: The defect is prioritised based on its severity and impact on the product. ↳ Defect assignment: The defect is assigned to a developer to investigate and fix. ↳ Defect fixing: The developer fixes the defect and verifies the fix. ↳ Defect Validation: The tester validates that the defect has been fixed and closes. ↳ Defect closure: The defect is closed after being fixed and validated. Note - This is not a defect life cycle -x-x- 950+ SDET interview Prep, Questions with answers and Coding questions exercises (paid): https://lnkd.in/gSU-m2F7 #japneetsachdeva

233

9 Comments