Caglar Candir

🎉 Day 24/365: Blogging Challenge 🎉 Today, I delved into the powerful AAA (Arrange-Act-Assert) pattern in test automation. This approach is key to writing clean, structured, and maintainable test cases. By separating tests into three distinct phases, the AAA pattern helps us focus on clarity and efficiency. 🔍 Arrange: Set up everything you need for the test. This involves initializing objects, preparing test data, and configuring the environment. 🚀 Act: Perform the actual operation you want to test. This is where you execute the code or functionality under test. ✅ Assert: Verify the results to ensure they match expectations. This is crucial for validating the behavior and outcomes of your code. Incorporating the AAA pattern into test automation frameworks, like Selenium C# with NUnit, enhances readability and maintainability, making it easier to debug and extend tests. Check out my latest blog post where I dive deep into the AAA pattern and provide coding snippets to illustrate its application: https://lnkd.in/d8jqFsM7 As I continue my 365-day blogging journey, I'm excited to share more insights and learnings with you. Stay tuned for more! #TestAutomation #Selenium #NUnit #SoftwareTesting #AAA #BloggingChallenge #SoftwareQuality #CodingBestPractices

7

How to find your first QA job if you are Switcher? Part 2. (You can find Part 1 and the first 3 points below on my feed) 4. Believe in yourself This is one of the most useful recommendations I received from two more experienced mentors. If you don't believe in yourself, why should recruiters and your future colleagues? Practices that can help to increase your self-belief: -write a list of your personal achievements -write a list of your achievements from previously work or study -look in the mirror every day and repeat at least 3-5 times: "I deserve the company I want. I deserve the salary I want. My skills and I are enough to achieve what I want"... Hug yourself after practice 5. Identify who your target audience is Try to analyse yourself from the outside and try to imagine which company might hire you. Where would you fit in? Describe this company. For example, a company is looking for someone more experienced than you, but invite you to the tech interview. Companies that might be your target audience: -have a strong mentoring programme within the company -are willing to invest time in you and help you develop your skills -value your strong soft skills and proactivity 6. Be open to any opportunities Any practice experience is useful for your next steps. Even a few months of commercial experience in any field will make you stand out among other candidates and can teach you useful things. If you're starting your journey in the QA field, be open to exploring new opportunities. Don’t miss out on internships, training sessions, tech meetups, or conferences. 7. Pet projects Practice on a realised products and attach the documentation to your CV. In my opinion, 5-10 good examples will be enough. 8. Improve your LinkedIn page Try to write about your first steps, share information that can be useful for people who have the same goals as you. Don't be discouraged if you don't get a lot of feedback from the Network, because even 1 like on your post is better than nothing, and for 1 more than you had a week ago 😅 Your posts are about communication and showing the way you think. Share it with the world, because your posts can work for you even months later when a recruiter to go to your page from your CV. Creating a great LinkedIn profile is an opportunity to communicate with recruiters without dialogue. Don't miss this chance to demonstrate why you are a strong professional – even without work experience. Some links that might be useful. Implement what resonates with you: https://lnkd.in/ej6wCFTz  https://lnkd.in/eSWD6G86 Remember – you are already is a part of QA community, just without job 😉

32

Why does strategy in QA matter? 🤔 Sure, having a test strategy doesn’t mean we can predict everything that will happen. But it sets us on the right course. 🧭 We might need to make adjustments along the way, but having that backbone makes it much easier to make decisions. A solid strategy is a reflection of all our QA actions throughout the software testing lifecycle. During test execution, I always refer back to it and stick to the plan until we release the software. Now, I know some agile teams tend to downplay strategy documents, focusing more on getting things done rather than writing things down… But trust me, having even a basic test strategy is key for planning and mitigating risks. ⚠️ Even in agile environments, capturing and documenting high-level activities can make all the difference—helping us finish test execution on time and without errors. When it comes to reviewing your test strategy, it’s not just about writing a one-off document—it’s about continuous improvement. Here are some crucial areas to keep revisiting: ⏰ The timeframe between introducing a new feature and getting it into users' hands—are you delivering updates efficiently and on time? 📊 The metrics and KPIs your team uses—are they accurate and truly representative? 🗣️ The communication flow and expertise level within your team—does everyone know each other’s roles and skill sets? ⛓️ The other processes that impact the time allocated for testing—does each lead to a better outcome? More on these below. 👇 By reviewing these regularly, you ensure you’re always on track to achieve the goals set out in your strategy. And don’t forget—this is a collaborative effort. Stakeholders need to stay in the loop, but it’s up to the QA lead to apply critical thinking, communicate effectively, and keep the bigger picture in mind. The goal? Make reviewing your test strategy less of a challenge and more of a puzzle to solve. 😉 #strategythinking #qastrategy #softwaretesting #qa #testingtips

22

❎ 𝐇𝐨𝐰 𝐭𝐡𝐞 𝐀𝐩𝐩𝐢𝐮𝐦 𝐚𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐜𝐨𝐧𝐭𝐫𝐢𝐛𝐮𝐭𝐞𝐬 𝐭𝐨 𝐭𝐡𝐞 𝐞𝐟𝐟𝐞𝐜𝐭𝐢𝐯𝐞𝐧𝐞𝐬𝐬 𝐨𝐟 𝐧𝐨-𝐜𝐨𝐝𝐞 𝐚𝐮𝐭𝐨𝐦𝐚𝐭𝐞𝐝 𝐭𝐞𝐬𝐭𝐢𝐧𝐠 🚀 1. 𝐀𝐛𝐬𝐭𝐫𝐚𝐜𝐭𝐢𝐨𝐧 𝐨𝐟 𝐂𝐨𝐦𝐩𝐥𝐞𝐱𝐢𝐭𝐢𝐞𝐬: Appium simplifies interactions with mobile devices and emulators, offering a user-friendly interface for testers. In no-code testing, this architecture supports visual interfaces, drag-and-drop tools, and intuitive frameworks, concealing the intricacies of coding and enabling testers to create automated tests effortlessly. 2. 𝐒𝐭𝐚𝐧𝐝𝐚𝐫𝐝𝐢𝐳𝐞𝐝 𝐀𝐮𝐭𝐨𝐦𝐚𝐭𝐢𝐨𝐧 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤: Appium adheres to the WebDriver protocol, a standardized approach for automating web browsers and mobile devices. This adherence facilitates seamless integration with no-code automation testing platforms, ensuring a consistent and reliable automation experience. 3. 𝐃𝐞𝐯𝐢𝐜𝐞 𝐈𝐧𝐭𝐞𝐫𝐚𝐜𝐭𝐢𝐨𝐧 𝐚𝐧𝐝 𝐂𝐨𝐧𝐭𝐫𝐨𝐥: The Appium architecture enables no-code automation platforms to interact with mobile devices and emulators. Without manual coding, testers can define actions through visual interfaces or intuitive tools, such as tapping, swiping, text input, and response validation. These platforms translate these actions into commands Appium understands, automating test scenarios effectively. 4. 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧 𝐅𝐥𝐞𝐱𝐢𝐛𝐢𝐥𝐢𝐭𝐲: Appium’s flexibility allows seamless collaboration with no-code automation platforms. Supporting various automation frameworks like Selenium, XCUITest, and UI Automator, the architecture enhances visual interfaces and drag-and-drop capabilities of no-code platforms, simplifying the overall no-code test automation process. 5. 𝐓𝐞𝐬𝐭 𝐄𝐱𝐞𝐜𝐮𝐭𝐢𝐨𝐧 𝐚𝐧𝐝 𝐑𝐞𝐩𝐨𝐫𝐭𝐢𝐧𝐠: Appium manages the execution of no-code automated tests on mobile devices and emulators. It captures defined interactions from the no-code test automation platform, translating them into device-specific actions. Appium also facilitates result reporting, empowering testers to analyze outcomes and identify areas for improvement in their no-code automated testing. 🖇 https://lnkd.in/gx5X2FtN #CodelessTesting #CodelessAutomation #AutomationTesting #Appium #TestingTools

2

Traps for new software QA engineers, common traps to avoid: Only Testing Happy Paths: Don’t skip testing for unexpected scenarios. Relying Too Much on Test Scripts: Think beyond the script to find real-world issues. Not Asking Questions: Always clarify doubts about requirements. Skipping Exploratory Testing: Do ad-hoc testing to uncover hidden bugs. Testing Without a Plan: Plan your tests to cover all areas. Ignoring Documentation: Record your steps and findings for consistency. Missing the Big Picture: Focus on overall user experience, not just single features. Avoid these to improve testing quality and build stronger skills! 💪 #SoftwareTesting #SoftwareQualityAssurance #SoftwareEngineering

7

Alert in Selenium is a message/notification box that notifies the user about some information or asks for permission to perform a certain kind of operation. It may be used for warning purposes as well. best link to practice JavaScript alerts: https://lnkd.in/gnCnxgjb Code: import io.qameta.allure.Description; import org.openqa.selenium.*; import org.openqa.selenium.edge.EdgeDriver; import org.openqa.selenium.edge.EdgeOptions; import org.openqa.selenium.support.ui.ExpectedConditions; import https://lnkd.in/gu_MM7c2; import org.openqa.selenium.support.ui.WebDriverWait; import org.testng.Assert; import org.testng.annotations.AfterTest; import org.testng.annotations.BeforeTest; import org.testng.annotations.Test; import java.time.Duration; public class Lab_325 { EdgeDriver driver; @BeforeTest public void openBrowser() { EdgeOptions options = new EdgeOptions(); options.setPageLoadStrategy(PageLoadStrategy.NORMAL); options.addArguments("--guest"); driver = new EdgeDriver(options); } @Test(groups = "QA") @Description("Test case description") public void testVerifyJSAlert() throws InterruptedException { // select box driver.navigate().to("https://lnkd.in/gnCnxgjb"); System.out.println(driver.getTitle()); driver.manage().window().maximize(); // //button[text()='Click for JS Alert'] // //button[@onClick='jsAlert'] // WebElement element = driver.findElement(By.cssSelector("button[onclick='jsAlert()']")); // WebElement elementConfirm = driver.findElement(By.xpath("//button[@onclick='jsConfirm()']")); WebElement elementPrompt= driver.findElement(By.xpath("//button[@onclick=\"jsPrompt()\"]")); elementPrompt.click(); //Aws, docker machine -> slow WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(3)); wait.until(ExpectedConditions.alertIsPresent()); Alert alert = driver.switchTo().alert(); // alert.accept(); alert.sendKeys("Atul"); alert.accept(); // alert.dismiss(); String result = driver.findElement(By.id("result")).getText(); // Assert.assertEquals(result,"You successfully clicked an alert"); // Assert.assertEquals(result,"You clicked: Ok"); // Assert.assertEquals(result,"You clicked: Cancel"); Assert.assertEquals(result,"You entered: Atul"); } @AfterTest public void closeBrowser() throws InterruptedException { Thread.sleep(5000); driver.quit(); } } #javascriptAlerts #selenium #Automationtesting #java #sdet

7

1 Kommentar

How can we handle the dropdown value selection in Selenium Java?😶 There are multiple methods to select a value from a dropdown. The Select class provides three primary methods: selectByVisibleText selectByIndex selectByValue Each of these methods is useful depending on the context and the type of comparison you need to perform. Methods to Select a Value from Dropdown 1. selectByVisibleText(String text): • When the visible text is known, Human-readable and straightforward Sensitive to text changes • Useful when you know the exact text of the option you want to select. dropdown.selectByVisibleText("Option Text"); 2. selectByIndex(int index): • It is useful when the position of the option is known, or when iterating through options. It is simple and fast but Index may change if the dropdown is modified dropdown.selectByIndex(2); // Selects the third option (0-based index) 3. ✅selectByValue(String value): • Selects an option by the value attribute of the option tag. • Useful when the value attribute is used unique and known. It is not affected by visible text changes but requires knowledge of the value attribute. dropdown.selectByValue("optionValue"); Choose the method based on your specific needs and the context of the dropdown you are working with. I personally use “selectByValue(String value)” which i found easy and reliable to use.

6

Real Challenges for QA Engineer: My Daily Reality Hello, LinkedIn community! 👋 I want to share what sometimes makes my job a real challenge—not to complain but to collaborate with you all to find better solutions. 1. Juggling Time and Quality — When projects race towards deadlines at full speed, I often have to make quick decisions about how deep to dive into testing details. It's always a tough choice that impacts the final product quality. Solution: Implementing agile methodologies can be extremely beneficial. We can better allocate time for thorough testing and adjustments by breaking down projects into smaller, manageable sprints. Additionally, using automated testing tools for repetitive tasks frees more time for complex test scenarios. 2. Vague Requirements—Ah, those moments when you start testing and the specifications raise more questions than they answer. This forces me to seek additional information, which can delay the process. Solution: I've found proactive communication and regular alignment meetings with the project team are crucial. Creating a detailed checklist of requirements before testing begins ensures that all parties understand and agree on what needs to be done. 3. Synergy with the Development Team — If there are communication gaps, the outcome can be far from perfect. These moments are frustrating, but they also show how important our cohesion is. Solution: Establishing a CI/CD pipeline can enhance collaboration. It allows for quicker iterations and immediate feedback, reducing misunderstandings and fostering a team environment where everyone is aligned on the project goals. 4. The Pressure of Compromises — Sometimes, it feels like everyone expects a "green light" from me, even when I see clear issues. It puts me in a difficult moral dilemma. Solution: Developing a clear risk management plan helps in making informed decisions. When faced with the pressure to overlook issues, having predefined criteria for critical bugs and a communication plan to present these findings to stakeholders can help mitigate the need for uncomfortable compromises. If you also work in testing, you've probably faced similar challenges. What are your strategies for dealing with them? I would appreciate any advice or techniques that have helped you. Thank you for being here, and I look forward to your stories and advice! 

3

1 Kommentar

An important resource

2

Through many projects I practiced using selenium I note that I have a problem with waits strategies ( not personal😅) , either these strategies are not working as I need or they not working at all, so I turned to Thread.sleep which is technically not recommended. but When I knew #SHAFT I think this problem solved because shaft has built in wait which saves time and decrease the numbers of codes written, if you think that this is the only thing SHAFT can do let me tell you that you are wrong and I'm just warm up. In my opinion the syntax of SHAFT is more readable than selenium, for example if you want to hover over an element in selenium you have to import Action and take instance and write down many codes but in SHAFT it's just one step you can directly hover over an element with a single line of code . Also reports in SHAFT is well formed you can exactly know what is the problem in youe code and it has a very good UI that gives you the advantage of knowing the results of your test precisely. Hard coded data is technically not supported and costs you time and effort because if you want to change,rerun or maintain something in your project you have to change the data in all related class that share the same data, so isolating your data in external files is a very good way to make your code and test cases easy to run many times without the need to change the data in many places, in selenium you have to make a class to read data _ whatever the way you read data with_ and write down many codes including the path in specific way, but in SHAFT it gives you a magic solution, you neither need a class nor many useless codes that may be complex, because you only want the path where is your data and put it in this way SHAFT.TestData.JSON registerData; public void enterYourData(){ registerData = new registerData(your path) } simple like that . all these information and more you can find in user guide which is written in a well formed form.

10

1 Kommentar

Should All BDD Scenarios Be UI End-to-End Tests? 🤔 It's a common question in BDD circles: Do all your BDD scenarios need to be UI end-to-end tests using tools like Selenium, Playwright, or Cypress? The answer: Not necessarily. The principle of the "lowest responsible level of testing" suggests verifying functionality at the lowest level where you can confidently illustrate the business logic—be it UI, API, or even unit tests. BDD scenarios should be implementation-neutral, focusing on business logic without locking you into specific UI interactions. This flexibility can make your testing process more efficient and maintainable. Watch more videos at - https://lnkd.in/e2Wsuu9K #SerenityDojoTV #TestAutomation #BDD #SoftwareTesting #QualityAssurance #AgileTesting #SerenityBDD #AutomationTesting #SoftwareDevelopment #CareerGrowth #SoftwareTester #AdvanceTesting #SoftwareTesters

2

Why do some QA engineers excel while others fall short? It all boils down to mindset. The top-tier QA professionals don’t just check boxes – they aim to conquer. They approach each bug as a puzzle and every test as an opportunity to demonstrate expertise. 🔍 Key Differences: 1️⃣ Elite QAs take ownership of their work, going above and beyond to ensure nothing slips by. 🧠 2️⃣ Lackluster QAs simply go through the motions, lacking drive and enthusiasm. 💤 3️⃣ Winners view challenges as chances to grow, whereas others view them as mere tasks. 🛠️ To excel in QA, emulate the winning mindset. Approach each task with the utmost importance and dedication. Mediocrity has no place in QA – strive to make the product flawless. 💥 #QAExcellence #OwnYourCraft #BeTheBest #QualityChampion

3

I want to present my own professional YouTube channel with 350 ISTQB Questions! 🚀 Develop your testing career with my professional YouTube channel "ISTQB Questions"! 🌐📚 📌 Start Comprehensive Training: Dive into our first two sets of videos, each a dynamic mix of questions, answers, and detailed explanations. 📌 Daily Videos: As we launch, we're committed to bringing you new videos every day. Expect a constant stream of information and guidance. This will allow you to not only pass the exam, but also to put what you've learned into practice in real projects. 📌 Engage and deepen your knowledge: Expand your knowledge by thoroughly studying each question worked through the ISTQB Syllabus and ISTQB Glossary. This approach promotes deep understanding of both complex and simple questions. 📌 Real-world application: We bridge the gap between theory and practice. Our videos contain real-life scenarios, allowing you to confidently apply what you've learned. 📌 Stay ahead of the curve: Sign up for our newsletter to stay up to date with the latest videos. 🔗 Click the link below to subscribe and start learning! 👇 https://lnkd.in/dnmT5dk4 🚀 Strengthen your testing skills, stand out in a competitive environment, and discover the future of software testing with my professional YouTube channel ISTQB Questions. Your success story starts here. 💡🌟 The first 316 questions at the Foundation Level v.4.0 (2023) are highly explained. Every day is a new question! https://lnkd.in/dwuxXRS8 The first 34 questions at the Advanced Level - Test Analyst v.3.1.2 (2022) are highly explained. https://lnkd.in/dK-Qqn7f * Author's subtitles in English have been added to all videos. Using the "Translate" button you can translate the video into any of the 125 languages ​​of the world.

2

Junior QA: - Doesn't know Git - Doesn't know how to review code programmatically - Doesn't know about testing techniques - Doesn't know how to write good test cases Semi-Senior QA: - Doesn't know Git - Begins to understand how to review code programmatically - Begins to understand about testing techniques - Begins to understand how to write good test cases Senior QA: - Begins to understand Git - Understands a little more how to review code programmatically - Understands about testing techniques - Understands how to write good test cases We have all been Juniors at some point. Without Juniors there are no Seniors. Let us learn to teach and be patient with those who want to build their careers. #qa #junior #senior #teach #learn #patie

25

6 Kommentare

💡 3 years ago, I started my QA journey. Key milestones: 📍 Started with manual testing 📍 Learned test automation 📍 Mastered CI/CD integration 📍 Led end-to-end testing projects Biggest lessons: 1. Quality is everyone's responsibility 2. Communication > Tools 3. Early testing saves time To junior QAs: focus on understanding the business logic first, tools second. #QualityAssurance #CareerGrowth #SoftwareTesting

5

2 Kommentare

Not all bugs are worth of fixing As a software tester, my job is to find bugs, report them and retest once the bugs are fixed. I always hated when bug stays in the backlog for a long time. But not all the found bugs should be fixed. The reasons why are quite simple: - They are limited to a specific use case used by a single customer - They are found on limited number of devices or systems - It would take too much effort to fix it without much gain - <insert here your reason> I have to admit, all of the reasons are related to money. We have to accept that fixing some bugs we find would take significant amount of development time. This amount of time costs money and it could be used for higher priority development. It is all about the return of investment (ROI). Of course, context matters. We cannot apply the same principles in e-commerce app testing and some medical device testing. And don't confuse bug reporting with bug fixing. Bugs should be reported but the decision on should they be fixed or not is open for discussion. I write about QA stuff. Today's piece of advice is to remind you that we are all on a budget. Follow me, visit https://qa-essentials.com and subscribe to my newsletter so you wouldn't miss any of the insights.

11

💡 How do you automatically rerun failed test cases in TestNG? 🔄 When running automated test suites, test failures can happen due to various reasons – network issues, flaky tests, or temporary glitches. Manually rerunning failed test cases can be tedious. Here's how to set up automatic retries for failed test cases in TestNG. 📌 Step 1: Implementing IRetryAnalyzer Create a custom retry class that implements IRetryAnalyzer. This will allow TestNG to retry a test case if it fails: import org.testng.IRetryAnalyzer; import org.testng.ITestResult; public class RetryAnalyzer implements IRetryAnalyzer { private int retryCount = 0; private static final int maxRetryCount = 2; // Number of retries @Override public boolean retry(ITestResult result) { if (retryCount < maxRetryCount) { retryCount++; return true; // Retry the failed test case } return false; // No more retries, mark as failed } } 📌 Step 2: Attaching Retry to Test Cases You can apply the retry logic to individual tests by using the retryAnalyzer attribute in the @Test annotation: import org.testng.annotations.Test; public class MyTest { @Test(retryAnalyzer = RetryAnalyzer.class) public void testMethod() { // Test code } } 📌 Step 3: Global Retry Using Listeners To apply this retry logic across all tests, implement a listener: import org.testng.ITestResult; import org.testng.TestListenerAdapter; import org.testng.annotations.ITestAnnotation; import org.testng.IAnnotationTransformer; public class RetryListener extends TestListenerAdapter implements IAnnotationTransformer { @Override public void transform(ITestAnnotation annotation, Class testClass, Constructor testConstructor, Method testMethod) { annotation.setRetryAnalyzer(RetryAnalyzer.class); // Global retry } } Don’t forget to add the listener to your testng.xml: <listeners> <listener class-name="com.example.RetryListener" /> </listeners> With this approach, TestNG will automatically rerun your failed tests, helping you save time and ensure better test reliability! #TestAutomation #TestNG #Selenium #AutomationTesting #Java #QA #RetryLogic #SoftwareTesting #FlakyTests #interview #job

10