Darshit Shah

Refining technical skills is not just a requirement for freshers and entry level QAs but also for experienced professionals who are targeting a promotion or good job switch. I often get asked about the technical skills required to excel in QA domain. I have written a small blog which discusses the same. #preplaced #QA #womenintech #freshers #opentowork #opportunities #SDET

15

QA Struggles 1on1: writing Smoke vs Regression suites. One of the most frustrating activities of a Manual QA tester is the task of writing, creating from a decisional position the Smoke/Regression suite. Reasons which make it difficult: 1. The pressure of having to be sure that the information adds testing coverage according to the suites nature. a. Smoke suites don't have to be very long and have to cover the core functionality. b. Regression suites are made up from a wide spectrum of testcases with different use-cases. 2. What to do when the app is feature heavy-loaded and the Smoke Suite exceeds a what you would call a Smoke Suite. 3. The better the code-coverage is the better your suite is, meaning less negative financial impact towards the company and less risks. What to do: - No matter which of the two suites you are tasked with providing be it Smoke or be it Regression always treat the idea of how much should you write in it as follows: a. Look at each feature as it were you are looking at a component for example: a searchbar". In doing so the QA has to discuss with the team in order to learn the inner-parts of the code and get used with the platform. b. Treat the core functionality of each component as part of the Smoke Suite. c. Treat all the rest of the scenarios from the core functionality as part of the Regression Suite. Why to do so? Why not to be scared of micro-manage your components? --- Because Smoke and Regression suites always go hand-in-hand with one another. There is no Sprint without executing a Smoke and a few days after a Regression Suite. This happens before delivering (demo meeting) the sprint's activity. By proceeding as such you have a lot of power when it comes with dealing with coverage, how much is too much and how much is too little? And also keep in mind that even if in doing so you find it hard to control the suites contents, then it's probably because the routine or procedures regarding the mandatory need of executing these suites per sprint in the presented order is not fulfilled and you don't have the assurance that you will actually tests those in a couple of days. Thank you for investing in yourself! #qa #newsfeed #news #invest #time #suites #development #java #C# #javascript #python #information #understanding #business #career

1

Types of errors in Tosca Verification-Failure: A failure that occurs when expectations and actual results do not match for the verification step. User Abort: This occurs when the tester stops the execution. Dialog-Failure: Apparently this is the result of some unhandled exceptions or steps. This error occurs when the application attempts to steer either a control that does not exist or is not in operation. #tosca #tricentis #testing #automation #TOSCA #QA

12

Automation is not complete until you know manual testing too. Manual testing is a base of your technical skills. You must have enough knowledge in order to test the product and also how to test the product with all prospectives. So only having automation things on your hand is not enough you must grasp knowledge of manual testing too. This is good for beginners atleast give it a read or save it for reading and understanding before an interview. #Learning #QA #SQA

38

2 Comments

What is Comprehensive Testing in Quality Assurance? QA involves a myriad of testing types, each serving a distinct purpose to ensure software functions seamlessly across various scenarios. Let’s delve into the key types of testing and their importance through a real-time example. 🔍 Unit Testing: Focuses on individual components. For instance, in an e-commerce application, unit tests would verify that the “Add to Cart” function works correctly, ensuring it updates the cart without errors. 🔗 Integration Testing: Ensures that different components work together. Continuing with our e-commerce app, integration tests would check that the payment gateway integrates properly with the cart and order processing systems. 🖥️ System Testing: Evaluates the complete and integrated software. Here, the entire e-commerce platform is tested to ensure it handles user registration, product search, order placement, and payment processing as expected. ✅ Acceptance Testing: Validates the software against user requirements. In our example, acceptance tests would involve real-world scenarios like a user placing an order, processing a return, or applying a discount code, ensuring the app meets all business requirements and user expectations. Comprehensive Testing in an E-Commerce Platform Consider an e-commerce application launch. The development team has built various features such as user authentication, product listings, cart functionality, payment processing, and order tracking. 1. Unit Testing: Developers write unit tests for each function—ensuring that logging in, searching for products, and adding items to the cart work flawlessly on their own. 2. Integration Testing: QA tests the interaction between components, like confirming that adding a product to the cart reflects correctly in the order summary and is processed accurately at checkout. 3. System Testing: The entire platform is tested end-to-end. A tester simulates the user journey from account creation to order completion to ensure all features work together without issues. 4. Acceptance Testing: Finally, the platform undergoes acceptance testing by business stakeholders or a sample group of end-users to ensure it meets all specified requirements and provides a smooth user experience. By leveraging this comprehensive testing strategy, the e-commerce platform can launch with confidence, providing a reliable and seamless shopping experience to its users. Effective QA is about more than just bug detection; it's about guaranteeing that software meets all quality standards and performs reliably in real-world conditions. #SoftwareDevelopment #QualityAssurance #ComprehensiveTesting #UnitTesting #IntegrationTesting #SystemTesting #AcceptanceTesting #SoftwareQuality #DevelopmentBestPractices #QARole #TechTrends #SoftwareEngineering #Ecommerce

4

2 Comments

Tip of #day8 for #21days21tips by The Test Chat : "Are you a software tester who wants to share their knowledge at conferences or Are you a software tester who wants to gain knowledge and grab networking opportunities at conferences? If the answer is yes for any of the above question(s) but you don't know how to know about different software testing conferences happening across the world, then I have a good news for you. You can always refer to the below site to know about software testing conferences happening worldwide: https://lnkd.in/dVqVbixy " #thetestchat #softwaretesting #community #conferences #conference2024 #shareyourknowlege #network #learnandgrow #tipoftheday

9

#SDET Interview Preparation Batch: https://t.ly/dIJZm Essential Interview Questions related to #Frame for Selenium. What is iFrame ? HTML element that loads another HTML page within the documen. Basically frame will be use to embed another website page into main windows as a advertisment. Cross Question. How can you communicate between the main window and the frame windows in a web page containing multiple iframes? FYI- One main window can have multiple frame windows and every frame html tag contains attribute like Id,name. Question - How To handle Frame Window? Ans - In order to handle frame windows, we should pass a driver control to frame window before a action. There are 3 ways driver control can be pass. 1️⃣ driver.switchTo().frame(String) The parameter String can be either the name or the id attribute of the iframe element. 2️⃣ driver.switchTo().frame(int) The parameter int represents the index of the iframe in the order they appear in the HTML document. 3️⃣ driver.switchTo().frame(WebElement) It allows you to switch to the iframe by directly passing the WebElement representing it. Question- How do you switch back to the default content after interacting with elements inside a frame? Ans-driver.switchTo().defaultContent() method. Question- 1️⃣ How do you identify if a webpage contains frames? 2️⃣ How to work with multiple frame ? 3️⃣ How to work with nested frame ? 4️⃣ can we pass driver control from one frame to another ? 5️⃣ how to work when frame does not have id, name, attribute ? 6️⃣ What happens if you try to interact with an element without switching to its frame first? 7️⃣ ***What are the challenges you might face when automating a webpage with frames? 8️⃣*** What is the significance of the `NoSuchFrameException` in Selenium WebDriver? #interview #QAinterview #AutomationTesting

184

2 Comments

Rethink Your Approach to a Career in QA! Don’t choose QA because you think it means no programming or avoiding code. If you believe that, you're setting yourself up for a short-lived career. To thrive in QA, you need to continuously enhance your skills. Key Skills Every QA Must Have: ▪️Databases ▪️APIs & Routes ▪️Security Checks ▪️UI/UX ▪️Problem Solving ▪️Programming Languages ▪️Version Control These skills overlap significantly with development. Just because you’re not strong in Data Structures or Algorithms doesn’t mean you can’t excel in QA or as a developer. I'm not discouraging anyone from choosing QA; I’m urging you to enter this field with the right mindset. QA is a legitimate field with immense international opportunities, significant salary growth, and a clear career path, including roles like: 🔹Automation Engineers 🔹Security Testing Engineers 🔹Performance Testing Engineers QA demands continuous learning and adaptation. Approach it with determination to develop your skills. Embrace QA for the dynamic and rewarding field it is. With the right mindset and skills, the sky's the limit!!!

104

6 Comments

🚀 #Day17 of #21Days21Tips with The Test Chat community! Today's pro tip: Tackling UI Test Automation Challenges! UI testing can be tricky, but with the right approach, we can overcome common hurdles like dynamic content, element locators, and test data management. 💪 By prioritizing robust test case design and leveraging cross-browser testing, we're ensuring our UI automation suites are reliable and effective. #QA #UIAutomation #TestingTips

20

#Selenium #Training #New #Batch Register : https://t.ly/kRNPk 🍀 Scenario Based Frequently Asked Interview Q&A on TestNG 🔺 Scenario: Handling Flaky Tests Question: How would you deal with flaky tests in your Selenium automation suite using TestNG? Answer: To address flaky tests, I would implement retry logic in TestNG. By using the retryAnalyzer feature in TestNG, I can specify a custom retry analyzer class that determines whether a failed test should be retried based on certain conditions, such as specific exceptions or test result statuses. This helps improve the reliability of the test suite by rerunning failed tests automatically. 🔺 Scenario: Parallel Execution Question: Explain how you would implement parallel execution of tests in TestNG for faster execution in your Selenium automation framework. Answer: TestNG allows running tests in parallel, either at the suite or test level, by organizing them into different suites and configuring parallel attributes like "parallel" and "thread-count". <suite name="MyTestSuite" parallel="tests" thread-count="5"> <!-- Test configurations --> </suite> 🔺 Scenario: Data-Driven Testing Question: Describe how you would perform data-driven testing using TestNG in your Selenium automation framework. Answer: TestNG supports data-driven testing through its @DataProvider annotation, which allows me to supply test data from external sources such as Excel sheets or databases. I can create a method annotated with @DataProvider to provide test data, and then annotate my test methods with @Test(dataProvider) to execute the tests with different data sets. This enables to execute the same test logic with multiple input values and verify the expected behavior. @DataProvider(name = "loginData") public Object[][] getLoginData() { return new Object[][] { {"user1", "pwd1"}, {"user2", "pwd2"}, }; } @Test(dataProvider = "loginData") public void loginTest(String username, String password){} 🔺 Scenario: Grouping and Tagging Tests Question: How would you group and tag tests in TestNG for better organization and selective execution in your Selenium automation framework? Answer: TestNG allows grouping tests using the @Test(groups) annotation, enabling selective execution and better organization of test suites by defining groups in testng.xml. This allows for selective execution of tests and better organization of test suites like smoke, sanity, regression. @Test(groups = {"smoke", "regression"}) public void loginTest() { // code }

174

3 Comments

🔍 Understanding the Difference: Sanity Testing vs. Regression Testing In the world of software testing, two critical methodologies ensure the stability and functionality of applications: Sanity Testing and Regression Testing. While they might seem similar, they serve distinct purposes in the QA process. Let's break it down: 🧠 Sanity Testing: * Purpose: To verify that a specific section of the application works as expected after a minor change or bug fix. * Scope: Narrow and focused on particular functionalities. * Execution: Performed manually to quickly check the validity of results. * Timing: Conducted after receiving a new build to ensure the new functionalities or bug fixes work correctly without deeper inspection. * Outcome: Determines whether it is reasonable to proceed with further testing. * Example: After fixing a login issue, we perform sanity testing to ensure the login feature works without diving deep into other functionalities. 🔄 Regression Testing: * Purpose: To ensure that recent code changes have not adversely affected existing features. * Scope: Broad and comprehensive, covering the entire application. * Execution: Often automated to efficiently handle extensive test cases. * Timing: Conducted after changes, updates, or enhancements to the codebase. * Outcome: Verifies that new code does not introduce new bugs and that existing functionality remains intact. * Example: Before a major release, we conduct regression testing to make sure that new features haven’t broken any existing functionality. 🤔 Why Both Are Crucial: Sanity Testing quickly checks for the rationality of changes, saving time before diving into more extensive testing. Regression Testing provides a safety net ensuring long-term stability and reliability of the software. By integrating both testing methodologies, we can maintain robust software quality, delivering reliable and high-performing applications to our users. #SoftwareTesting #QualityAssurance #SanityTesting #RegressionTesting #SoftwareDevelopment #QA

27

🚀 Why Manual Testing Matters in Software Testing🚀 In the realm of software testing, the debate between manual and automated testing is ongoing. While automated testing offers speed and efficiency, manual testing remains an indispensable part of the process. Here's why: 1. Human Judgment: Manual testers bring critical thinking and intuition to the table, catching issues that automated scripts might overlook. #HumanJudgment #CriticalThinking 2. Exploratory Testing: Manual testers can delve into the software, uncovering unexpected issues and edge cases. #ExploratoryTesting #UncoverTheUnexpected 3. Adaptability: Manual testing easily adapts to changing requirements and user feedback, making it ideal for agile environments. #AdaptableTesting #AgileQA 4. User Perspective: Manual testing provides insights into usability and user experience, ensuring software meets user needs. #UserExperience #UsabilityTesting 5. Early Bug Detection: Manual testing catches bugs early, preventing them from becoming costly issues later on. #EarlyBugDetection #PreventiveTesting 6. Complex Scenarios: Certain scenarios demand human intervention due to their complexity. Manual testing shines here. #ComplexScenarios #HumanTouch 7. Validation of Automated Tests: Manual testing validates automated scripts, ensuring accuracy and effectiveness. #ValidateTests #QualityAssurance In conclusion, manual testing complements automated testing, offering the human touch necessary for software quality and a seamless user experience. 🔍 Let's discuss the importance of manual testing in software QA! #ManualTesting #SoftwareQuality #QAInsights

25

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

328

8 Comments