Sudharsan Selvaraj

🚀 𝗚𝗲𝘁𝘁𝗶𝗻𝗴 𝗦𝘁𝗮𝗿𝘁𝗲𝗱 𝗶𝗻 𝗧𝗲𝘀𝘁 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 🛠️ Are you looking to launch a career in Test Automation Engineering?  𝗪𝗵𝘆 𝗖𝗵𝗼𝗼𝘀𝗲 𝗧𝗲𝘀𝘁 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴? 1. 𝙃𝙞𝙜𝙝 𝘿𝙚𝙢𝙖𝙣𝙙 📈  - The tech industry is rapidly growing, and there’s a significant demand for skilled test automation engineers to ensure software reliability and efficiency. 2. 𝘾𝙤𝙢𝙥𝙚𝙩𝙞𝙩𝙞𝙫𝙚 𝙎𝙖𝙡𝙖𝙧𝙞𝙚𝙨 💰  - Enjoy competitive salaries and excellent growth prospects. 3. 𝘾𝙖𝙧𝙚𝙚𝙧 𝙎𝙖𝙩𝙞𝙨𝙛𝙖𝙘𝙩𝙞𝙤𝙣 😊  - This role offers a perfect blend of creativity, problem-solving, and technical skills, leading to high job satisfaction.  𝗦𝘁𝗲𝗽𝘀 𝘁𝗼 𝗕𝗲𝗰𝗼𝗺𝗲 𝗮 𝗧𝗲𝘀𝘁 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿: 1. 𝙀𝙙𝙪𝙘𝙖𝙩𝙞𝙤𝙣𝙖𝙡 𝘽𝙖𝙘𝙠𝙜𝙧𝙤𝙪𝙣𝙙 🎓  - A degree in Computer Science, Information Technology, or a related field is beneficial but not always necessary.  2. 𝙇𝙚𝙖𝙧𝙣 𝙋𝙧𝙤𝙜𝙧𝙖𝙢𝙢𝙞𝙣𝙜 𝙇𝙖𝙣𝙜𝙪𝙖𝙜𝙚𝙨 💻  - Python: Widely used for its simplicity and efficiency in writing test scripts.  - Java: Commonly used in enterprise environments.  - JavaScript: Popular for web application testing. 3. 𝙐𝙣𝙙𝙚𝙧𝙨𝙩𝙖𝙣𝙙 𝙎𝙤𝙛𝙩𝙬𝙖𝙧𝙚 𝙏𝙚𝙨𝙩𝙞𝙣𝙜 𝙁𝙪𝙣𝙙𝙖𝙢𝙚𝙣𝙩𝙖𝙡𝙨 🧠  - Gain a solid understanding of software testing principles, including unit testing, integration testing, system testing, and acceptance testing. 4. 𝙂𝙚𝙩 𝙁𝙖𝙢𝙞𝙡𝙞𝙖𝙧 𝙬𝙞𝙩𝙝 𝙏𝙚𝙨𝙩𝙞𝙣𝙜 𝙁𝙧𝙖𝙢𝙚𝙬𝙤𝙧𝙠𝙨 𝙖𝙣𝙙 𝙏𝙤𝙤𝙡𝙨 🛠️  - Selenium: A widely-used tool for automating web applications.  - JUnit/TestNG: Popular testing frameworks for Java.  - Cypress: An all-in-one testing framework for web applications.  - Jenkins: For continuous integration and continuous deployment (CI/CD). 5. 𝘿𝙚𝙫𝙚𝙡𝙤𝙥 𝘼𝙪𝙩𝙤𝙢𝙖𝙩𝙞𝙤𝙣 𝙎𝙘𝙧𝙞𝙥𝙩𝙨 📝  - Start writing basic test scripts and gradually move to more complex automation scenarios. 6. 𝙏𝙖𝙠𝙚 𝙊𝙣𝙡𝙞𝙣𝙚 𝘾𝙤𝙪𝙧𝙨𝙚𝙨 𝙖𝙣𝙙 𝘾𝙚𝙧𝙩𝙞𝙛𝙞𝙘𝙖𝙩𝙞𝙤𝙣𝙨 📚  - Enroll in courses on platforms like Coursera, Udemy, and LinkedIn Learning.  7. 𝙂𝙖𝙞𝙣 𝙋𝙧𝙖𝙘𝙩𝙞𝙘𝙖𝙡 𝙀𝙭𝙥𝙚𝙧𝙞𝙚𝙣𝙘𝙚 💼  - Work on real-world projects, internships, or freelance opportunities. Practical experience is crucial. 8. 𝘽𝙪𝙞𝙡𝙙 𝙖 𝙋𝙤𝙧𝙩𝙛𝙤𝙡𝙞𝙤 🌟  - Create a portfolio of your automation projects. Use platforms like GitHub to display your work to potential employers. 9. 𝙎𝙩𝙖𝙮 𝙐𝙥𝙙𝙖𝙩𝙚𝙙 𝙬𝙞𝙩𝙝 𝙄𝙣𝙙𝙪𝙨𝙩𝙧𝙮 𝙏𝙧𝙚𝙣𝙙𝙨 🔄  - Follow industry blogs, join testing communities, and attend webinars and conferences, staying current is essential. 10. 𝙉𝙚𝙩𝙬𝙤𝙧𝙠 𝙬𝙞𝙩𝙝 𝙋𝙧𝙤𝙛𝙚𝙨𝙨𝙞𝙤𝙣𝙖𝙡𝙨 🤝  - Connect with test automation professionals on LinkedIn, join relevant groups, and participate in discussions.  Try this learning path https://lnkd.in/gtjYWNPF #TestAutomation #CareerGrowth #SoftwareTesting #QualityAssurance #Selenium #Python #Java #Cypress #ContinuousLearning #ProfessionalDevelopment

1

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Get SDET Interview ready with my latest updated package (paid): https://lnkd.in/gusymgFi Read & Follow me on Medium for tech related blogs: https://lnkd.in/dCDi84Q9 #japneetsachdeva

261

8 Comments

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Note: All services on TopMate are discounted till 31st May. Use it maximize your learning!! Get SDET Interview ready with my latest updated package (paid): https://lnkd.in/gusymgFi Full Stack QA with Test Architect preparation: https://lnkd.in/dWjpT3-3 Read & Follow me on Medium for tech related blogs: https://lnkd.in/dCDi84Q9 #japneetsachdeva

153

9 Comments

Top 15 API Terms every SDET should know! 1) API: Clients request resources or services that the server performs. The way in which these two parts usually communicate is through an API. 2) API Orchestration: Combining data from multiple services and presenting it to client or application for further interactions. 3) API Gateway: A single entry point for all clients. It helps balance the load to the endpoints received from different clients and manages traffic. 4) API Key: One of the authentication mechanism, where unique keys are used by each client for further usage. 5) API Request: API request is the set of details needed to submit to the server to understand and respond properly. 6) API Response: After sending the details as a request, the server interprets and sends the response back to the client. 7) BaseURI: Base Uniform Resource Identifier is the complete path used to locate a specific resource (Base URL, which is the application URL + path) 8) API Contract: Contract: An agreement details what the consumer can expect from the API. Take a look at google outh 2.0 contract: https://lnkd.in/gpZ2ZGZw 9) CORS:  Cross-Origin Resource Sharing (CORS) is an HTTP-header-based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Note: CORS errors are one of the most common issues in API Testing. 10) HTTP methods: An HTTP request is an action to be performed on a resource identified by a given Request-URL. Request methods are case-sensitive. The most common ones are: GET, POST, PUT, and DELETE. 11) HTTP Headers: Headers are the additional but essential information sent as part of the request details from the client for the server to understand the client. Such as Content-Type, Tokens etc. 12) Pagination of APIs: Offset Pagination: is the simplest method; “limit” and “offset” values are used here. Keyset Pagination: uses the filter values of the previous page to determine the next set of items. 13) Parameters: API Parameters are passed along with the endpoint URL, which helps filter resources. Path/Query params are the most frequently used ones. 14) Status Codes: The list of numeric codes followed by a message returned from the server to the client. Client error codes: starts from 4xx, Server error codes: starts from 5xx. 15) SSL Certificates: SSL certificates create a foundation of trust by establishing a secure connection. It is a small data file that cryptographically establishes an encrypted link between a web server and a browser. -x-x- Get SDET Interview ready with my latest updated package: https://lnkd.in/gusymgFi Become Master in Test Automation Frameworks & Designs: https://lnkd.in/gyFKz5yF My latest course on Udemy, for sale at Rs 399 only, Take a look here: https://lnkd.in/grvCi-ri #japneetsachdeva

145

2 Comments

If you're afraid of layoffs as an SDET professional. (Here's a proven strategy to strengthen your career security) 4 years ago, I lost my job. This experience, while scary at first, helped me grow my career and earn much more money than before. Here's how: After college, I started my career at a big company and worked there for 5 years, including my internship. I got comfortable and never really thought about improving myself or sharpening my skills. Then, in 2020, the pandemic hit. My manager said some people might lose their jobs because the company was not doing well. That announcement was a wake-up call. I started learning new skills on Udemy, and before my last day at work, I got a job offer that paid 40% more than my old job. My current salary is 10 times what it was before! If you're scared of layoffs or stuck in a low-paying job, Here are 4 actionable tips I used to strengthen my career security. ( You can do them too ) 1) Learn new things to stay valuable in the job market. 2) Always be on the lookout for new job opportunities. 3) Reflect on past job interviews to improve for the future. 4) Practice coding and technical skills regularly. Don't wait for a layoff to make a change. PS: Have you been laid off before? -------------------------------------------------------------- If you need advice on your career, feel free to schedule a 1:1 consultation using the link in the comment section to discuss your specific SDET career goals. -------------------------------------------------------------- Follow Manish Saini for more such content. #CareerGrowth #Resilience #Upskilling #CareerTransition #SDET #Mentorship #MondayMotivation

147

7 Comments

When I started testing, I was often asked to write a test plan for < a feature >. Or, sometimes, I’d be handed a 50 pager with the ask to “review the test plan”. These plans commonly detailed things like environment setup, OS, test steps, and other minutiae of how exactly the testing of < a feature > was to be executed. These days, I much prefer to write test strategies - instead of detailing every step, which inevitably leads to a lot of rework throughout the development process, we think strategically about how we can test certain aspects of our application, what kind of tests we’ll need and if those can be automated or if they’re one offs that benefit from human execution. Think blueprint vs. construction manual. What are your experiences with one or the other?

74

10 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

152

5 Comments

Many times in the past 1-2 weeks, I felt like taking a deep dive into "test cases" or "tests". I feel that the phrase "test case" came from IT services/Captives world of testing and word "Test" originated from software product companies like Microsoft/Google/Adobe. In a connected world (where IT services and Product company testing cultures collaborate) - the word test case without any qualification - typically means a "open" format, step-by-step "instructions" written in natural language such as English - directing the tester in terms of what to do during testing. Test cases will eventually needed to be "Automated" to save the cost of testing and gain the speed (questionable... at times). Test cases are written by "manual" testers or Non technical testers. Test cases are supposed to encapsulate the "domain" expertise of Business analysts or "experienced" manual testers. Test cases are also written down (at times in a very detailed format) so that a "low cost", junior (or literally anyone) testers. The word test, on the other hand, closely connected to (or is) "unit test" - is a developer friendly "code" written. As in "a good developer writes tests always along with feature/product code". Unlike test cases - tests are already code and hence do not need to be "automated" at a later point of time. Since tests are already code there is no accompanying or mapped "test cases". Tests are developed by developers or SDETs. Will expand more on following - Integrating worlds of "Tests" and "Test cases" - Format and level of details in "Test cases" - What makes a good test case or test? Will the goodness a constant attribute or something that goes down with usage?

3

Big mystery of the century solved !!! Manual testing means testing using "instructions manual" not what we always thought as "Not using automated tests" Way to go Lalitkumar Bhamare /Pun alert/ Test case documents with detailed steps are called "Instruction Manual" for testers. You will be instructed to follow the "manual" strictly - failure to do it will result in you discovering bugs in the application. Do it at your own risk. Make sure take screen shots at every possible step to protect yourself from any "auditor" quizzing you for hours "How can you prove that you executed that test step". You could lose your job for your inability to prove it.

11

In my journey of testing and automation, I had plenty of opportunities to talk to company CEOs, CTOs, QA Heads etc telling me that they have test automation team but their most of the releases are manual and are still buggy with trivial issues. One thing that I am damn sure about is no amount of testing/automation is going to help you if you do not have a proper process. A proper release process is what you need and then a well planned testing and automation is going to make the release faster and better. Bugs in production is not the disease, it's a symptom that your release process is broken. I have applied my learning in 3 of the organisations that I worked recently and found that fixing process has fixed most of the issues in product. Even though I joined as automation architect or QA leader, my role soon became a cross function POC helping Business, Product and Engineering work in sync and make a better product.

102

12 Comments

Check out my latest blog article!

19

1 Comment

Do All Acceptance Criteria Need to be Automated with Cucumber in BDD? Hey folks, John Ferguson Smart here! Let's dive into an important question for those practicing BDD: Do you need to automate every acceptance criterion with Cucumber? 🔹 Key Insights:   - Flexibility in Tools: Discover why BDD isn't confined to Cucumber and how different tools like JUnit or PyTest can also be effective.   - Focus on Process: Learn the significance of the conversation with your product owner, identifying examples, and creating shared understanding.   - Executable Specifications: Understand the value of writing tests as executable specifications and producing living documentation, regardless of the tool. In this video, we explore the core values of BDD and emphasize the importance of the process over the specific tools used. #SerenityDojo #BDD #TestAutomation #SoftwareTesting #AgileTesting #TestingTips

6

Why Playwright is better then Selenium? I'll list down some straight forward advantages that Playwright has over Selenium: 1. No special code to handle browsers like selenium 2. Storage state 3. Built in Reporting and screenshots 4. Retries are made easier 5. Auto waiting and retry assertions 6. VScode extension 7. Isolated sessions 8. Simple integration with GitHub Actions 9. UI Mode and Trace Viewer 10. Does API Testing and is great at it 13. Grouping tests using a Describe Block 14. Accessibility Testing 15. Not having to manage drivers for the Browsers 16. Infinitely better Locator strategies Now, let's breakdown if Playwright framework is really better then Selenium Framework! : Reporting supported by Playwright is only available with JS, except this I think all other pros mentioned are far better in Playwright over Selenium. But what you do? If you are looking for a new job? Learn Selenium or Adopt Selenium as its a go to! Why? Because most of the teams have already invested heavily on its Framework setup and execution cycles.

13

✨Common Selenium Exceptions ✨ When working with Selenium, facing exceptions is part of the process. Here’s a quick guide to handle them effectively:⬇️ #NoSuchElementException: 🔹Occurs When: The element you are trying to locate does not exist in the DOM. 🔸Handling: - Use explicit waits to ensure the element is present. - Verify that the locator (ID, class, XPath) is correct. #TimeoutException: 🔹Occurs When: An operation exceeds the specified wait time. 🔸Handling: - Increase the wait time or use explict wait with specific condition #ElementNotVisibleException: 🔹Occurs When: The element is in the DOM but not visible. 🔸Handling : - Scroll to the element to bring it into view. - Ensure the element is not hidden via CSS or use JavaScript to make it visible. #StaleElementReferenceException: 🔹Occurs When: The element is no longer attached to the DOM. 🔸Handling: - Relocate the element just before interacting with it. - Ensure the DOM is stable and not frequently changing -Increase the wait time or use explict wait with specific condition #NoSuchFrameException: 🔹Occurs When: Attempting to switch to a non-existent frame. 🔸Handling: - Verify the frame locator is correct. - Ensure the frame exists in the DOM before #Selenium #AutomationTesting #WebDriver

3

🚀 Unlocking Test Automation Superpowers: Cucumber + TestNG Integration 🥒 Introduction: Welcome to the dynamic duo of test automation! 🌟 Discover how to fuse the natural language magic of Cucumber 🥒 with the robust testing prowess of TestNG 🧪. Get ready to supercharge your testing strategy and unleash the full potential of your automated tests! 💥 1. Cucumber and TestNG: A Match Made in Testing Heaven: 📝 Cucumber: Write tests in plain English, making them easy to understand for everyone. 🛠️ TestNG: Power-packed testing framework with advanced functionalities and reporting capabilities. 2. From Scenarios to Tests: The Seamless Conversion Process: 🔄 Easily convert Cucumber scenarios into TestNG tests using Cucumber's test runner class. 🎯 Map each scenario to a TestNG test method for smooth execution and precise reporting. let us understand the same using demonstration: https://lnkd.in/dWqjvj5K 3. Turbocharge Your Testing with Parallel Execution: ⚡ TestNG's built-in support for parallel execution ensures lightning-fast results. 🔧 Configure parallel execution at various levels to maximize resource utilization and minimize execution time. let us understand how to configure and execute test cases parallelly: https://lnkd.in/dYa95i4i Conclusion: 💪 Embrace the synergy of Cucumber and TestNG to revolutionize your test automation journey. With seamless integration, effortless scenario conversion, and lightning-fast parallel execution, you'll elevate your testing game to unprecedented heights. Get ready to conquer the testing universe with confidence and flair! 🚀🥒🧪

34

2 Comments

Design principles are critical to ensure high-quality software development. Here are some design principles commonly applied at different stages of SDLC: 1. SOLID (Applicable to Classes / Modules / Functions etc.) - Single Responsibility Principle : One reason to change. - Open / Closed Principle : Open for extension but closed for modification.(plug in an extension board and extend an existing electric adapter fitted into the wall) - Liskov Substitution Principle : SubTypes should be substitutable with BaseType without altering the program's correctness. (e.g pointer to base class object can accept derived class objects ) - Interface Segregation Principle: Should not be forced to depend on interfaces that they don't use (Split large interfaces) - Dependency Inversion: High level module should not depend upon low level modules. (Use abstractions) 2. KISS (Keep it simple, stupid): Emphasizes simplicity in the design and implementation, reduces user training, helps in maintenance. 3. DRY (Don't repeat yourself): Avoid duplication by abstracting common functionality into reusable components. Helps in productivity/defect fixing and code maintenance. 4. YAGNI (You Ain't Gonna Need It): Don't implement feature until you require it. Requirement might get changed and can impact overall flow and adds up more rework. 5. Single Source of Truth (SSOT): Helps to avoid inconsistencies and data integrity. (Good for designing Central Data) 6: Fail-Fast Principle : Report errors as soon as it occurs. (Helps systems not to be flooded with retries etc , good for interface/API integration) 7. Loose Coupling / High Cohesion : Minimize dependencies and ensure closely related modules are grouped together to avoid over-splitting the modules. 8. Security By Design (SbD): Incorporate security at every stage of software life cycle. etc.

8

1 Comment

#Jmeter is more efficient because it adapts in flight given it’s open source software coupled with contributors around the world. You always keep the scripts and understand how to operate professionally with Jmeter. #LoadRunner was once a very strong product that I sold myself for HP when it was the only platform you needed for testing. Those days are long gone. It’s proprietary software that’s changed hands many times now, and exists to serve teams that aren’t adapting in flight with testing to continuously deliver fast & strong user experiences that materially influence the top & bottom line. Corporations will not continue nurturing and sculpting a proprietary platform past its prime to do anything beyond the basics to ensure renewal revenue is captured while investing marginally into R&D. OctoPerf properly delivers the next level with #EnterpriseJmeter Designed to adapt in flight in lock-step with open source Jmeter perpetually while extending powerful capabilities on top of Jmeter and across the entire Octoperf platform. OSS is simply better design for testing platforms over time because it’s essentially a utility for… Organizations that value efficiency . . .Teams that demand the best . . . . . .Pursuing testing excellence always I can personally guarantee Octoperf’s core team is wonderful and quite skilled. Octoperf is on a proper trajectory building a truly global brand with a robust platform you can bet your business, job, and sanity on today and tomorrow. #PerformanceMatters

1

Question by Shivam Bharadwaj What are my thoughts on shift left testing, test cases != testing and automation!=testing? My response Shift left testing. Testing is testing. There is nothing on the left side, right side, front side or back side. Shift left is just a term created out of the blue just to mean start testing early on which is expected and not an exception. People are so used to testing after the build is created by developers that someone created a term "shift left" to denote start testing towards the left side of SDLC phase. Now you can guess, shift right is testing in production. I am not a big fan of testing in production since the risks outweigh the benefits. The kind of defects that you can find in production are below which you cannot find in lower environment. 1. Prod certificate expirations 2. Defects due to specific data that exists only in production. 3. Configuration issues. 4. Infra issues. and few more. Ideally, there will never be any functionality issue that you cannot find in well created lower environment which ideally should mimic production environment as closely as possible. Testcases != testing Testcases are a drop in an ocean called testing. Automation!= testing Automation is a friendly companion to testers for testing efficiently and freeing them to test better. #testing #automation #softwareengineering

106

12 Comments