Microservices are a popular architectural style for building modern applications that are scalable, resilient, and adaptable. Instead of developing single, monolithic applications, we have seen the advent of microservices that break down functionality into smaller, independent services that communicate with each other through well-defined interfaces. Microservices offer many benefits over monolithic architecture. These benefits include faster and easier development, improved fault tolerance, and better overall performance. Although the sun is shining, clouds can be seen looming in the distance. That is because although microservices are great, it can introduce new challenges and complexity, especially when it comes to testing them. Microservices testing is not the same as testing a monolithic application. Microservices might have multiple dependencies, configurations, and interactions that need to be verified and validated between one another. Moreover, microservices need to be tested across different levels of granularity, as well. This can range from individual microservices to the entire end-to-end system. This is why automated software testing is essential for the development and delivery of microservices. Automated testing can help achieve faster feedback, reduce human error, and facilitate continuous delivery. In this blog post, we will discuss different types of tests, best practices and strategies for automated testing of microservices, and tools that can help expedite the testing process.
Different Types of Tests for Microservices
Microservices automation testing will include taking advantage of a collection of different types of tests that cover different aspects and levels of the system. Some of you might be familiar with some of these types of tests already, but some of the common types of tests utilized when testing microservices include:Unit Tests: These are basic tests and are the most granular. They verify the functionality and behavior of individual components or units of code. Unit tests are usually written by developers and are sometimes the first line of defense against issues, errors, and bugs that might be present in the application.
Component Tests: These are tests that check the functionality and integration of a single service or possibly a group of related services. Component tests are more comprehensive than unit tests because they involve testing the service’s interfaces, dependencies, data, and different configurations.
Integration Tests: These tests verify the communication between multiple services. Integration tests ensure that these services work together as expected and handle errors as they should, preferably gracefully. Should the services fail to communicate with one another, the entire application would be fatally flawed.
Contract Tests: These are tests that validate the contracts or agreements between services. Contracts define the expectations and obligations that each service might have. This might include input, output, formatting, and overall behavior. Contract tests help avoid breaking changes and ensure that the services are compatible with one another.
End-to-End Tests: These are tests that simulate the user’s journey. It also considers the user’s experience with the entire application or system. These are key to checking both system functionality and performance as well as validating the usability of the system, all from the user’s perspective.
Benefits of Automated Microservices Testing
Automated testing is the process of executing tests – often in the form of scripts – that verify and validate results without human intervention. There are also tools out there on the market that are meant to help with automated testing. Automated testing has many advantages over manual testing, especially in the context of testing microservices. Some of the benefits of automated testing include:
Faster Feedback: Automated testing can run faster and more frequently than manual testing. This gives the testers and developers immediate and continuous feedback. Furthermore, it helps identify and fix bugs earlier on in the software development lifecycle (SDLC). Ultimately, it aims to improve quality and reduce rework.
Reduced Human Error: Automated testing can remove the human part of the equation, thus reducing or eliminating human errors and inconsistencies. These errors and inconsistencies are often found throughout manual testing and can include typos, oversights, and general fatigue. This helps ensure accurate, reliable, and repeatable tests and results.
Facilitated Continuous Delivery: Automated testing can enable continuous delivery or the practice of delivering software updates to users in small and frequent increments. Continuous delivery often requires a high degree and level of automation. This helps to reduce risks, increase efficiency, and get your product on the market faster.
Although automated microservices testing seems to have all the bells and whistles, it’s not a silver bullet, though. It has some challenges and limitations that come along with it, such as initial cost, maintenance, the learning curve that comes with automation (even using a tool), and can have a high degree of complexity depending on the given scenario, use case, or industry. On that note, it’s important to balance the trade-offs and choose the right tool or type of automation for your requirements and needs.
Best Practices for Automating Microservices Testing Automating microservices testing is not a one-size-fits-all approach. It often requires careful planning, execution, and evaluation. Following some best practices and strategies can help and go a long way, here are some to think about:
Handle Dependencies: Microservices have many dependencies. These can be other services, databases, and APIs, among other things. These dependencies can often affect the test results and cause failures or delays. As such, it’s important to handle the dependencies properly, such as using techniques like mocking, stubbing, or service virtualization, etc.
Test Different Configurations: Microservices can run in different environments, like development, staging, production, etc. These environments often have different configurations, data, and resources, all of which can impact both the behavior and performance of the microservices. Therefore, it’s important to test the services in different setups.
Prioritizing Test Coverage and Maintenance: It’s crucial to prioritize test coverage to focus automation efforts on critical functionalities. Conducting risk analysis and identifying high-priority test scenarios helps in allocating resources effectively. Additionally, maintaining automated tests is essential for their long-term effectiveness. Regularly review and update tests to accommodate changes in requirements, user interface, or underlying code.
How Qyrus Helps in Automating Microservices Testing Qyrus is a simple, smart, and scalable platform that covers all your testing needs. We can test end-to-end business processes, web applications, mobile applications, and APIs. What’s more is that Qyrus is there to help automate the testing of your microservices. Qyrus can help in in different ways such as:
Supporting the testing of REST, SOAP, and GraphQL APIs, all with a codeless approach that also goes for testing web apps and mobile apps. You can easily build and create test scripts, execute them, and manage these test scripts on one platform. Furthermore, test the functionality of your APIs as well as their performance using Qyrus’ intuitive interface and supporting features.
Handling all of the infrastructure needs, as well. Test your services and apps on different browsers, devices, and operating systems using Qyrus’ cloud-based browser and device farms. Execute your tests in parallel, as well, cutting down test execution time and getting results back faster.
Read about our success story with Waste Management and how we’ve helped facilitate their API testing which has prevented any bugs from being introduced into production over a 24-month period. This client tests over 400+ endpoints running 4500+ tests in less than 5 minutes, all done through their CI/CD integration.
Providing real-time test reports, analytics, and insights to help you monitor and improve your testing processes and outcomes. You can also collaborate with your testing teams and stakeholders using Qyrus’ communication and notification features.
Qyrus is a next-generation testing platform infused with AI that combines the power of open-source frameworks with the simplicity of codeless testing. Qyrus can help you automate microservices testing faster and more efficiently. With Qyrus, deliver value to your customers sooner! If you want to try out Qyrus for yourself, you can sign up for a free trial or contact us for a custom solution today!
Conclusion Microservices are a powerful way to build modern applications that are scalable, resilient, and adaptable. However, microservices also require a different approach to testing when compared to testing traditional monolithic applications, one that is more comprehensive, rigorous, and automated. Automated software testing is vital for the development and delivery of microservices. It can help achieve faster feedback, reduce human error, and facilitate continuous delivery.
To automate microservices testing, we need to use the right tools and frameworks, such as Qyrus! By automating software testing for microservices, we can ensure the quality, reliability, and functionality of our applications. We can deliver value to our customers faster and much more efficiently. If you want to learn more about automated testing, feel free to check out some more of our blog posts. To get to know more about Qyrus specifically, check out our Feature Friday series or contact us today!
In the dynamic landscape of software development, Application Programming Interfaces (APIs) serve as the backbone of modern connectivity. They enable seamless communication between diverse applications and systems. With various types of APIs emerging, including RESTful APIs, GraphQL, SOAP, etc., developers have many options when designing their integration solutions.
As businesses increasingly rely on API platforms to deliver robust, interconnected solutions, ensuring the reliability and efficiency of these interfaces becomes paramount.
This is where API testing steps in. It offers a comprehensive approach to validate APIs’ functionality, reliability, performance issues, and security. As per AI Multiple Research, the main factors behind using APIs in organizations are as follows:
Now that we know the landscape of APIs, let’s explore the world of API testing and uncover the benefits of API testing.
What is API Testing and API Testing Automation?
API testing entails rigorously examining APIs to ensure they behave as expected, interact seamlessly with external systems, and adhere to predefined specifications. It is a critical component of the software development lifecycle. It enables organizations to identify and rectify issues early on, enhancing overall product quality and user experience.
API testing automation, on the other hand, leverages specialized tools and frameworks to streamline the testing process, improving efficiency and accuracy. AI/ML intelligence also plays a pivotal role in API testing automation.
Industry statistics indicate that the global API Testing market was valued at US$538.9 million in 2022. It is projected to reach US$1452.4 million by 2029, at a CAGR of 15.2%.
Benefits of API Testing Automation Understanding the benefits of API testing and its diverse types is essential in ensuring the reliability and functionality of critical interfaces. Types of API testing encompass a broad spectrum, including unit testing, integration testing, functional testing, security testing, and more.
API performance metrics also play a pivotal role in assessing the efficiency and responsiveness of APIs, ensuring optimal user experiences. Metrics such as response time, throughput, and error rates provide valuable insights into an API’s performance under various conditions.
Moreover, integrating API testing into a Continuous Integration and Continuous Deployment (CI/CD) pipeline is crucial for maintaining quality and efficiency throughout the software development lifecycle. By automating the execution of test cases within CI/CD pipelines, teams can ensure rapid feedback loops. They can also detect early bugs and seamlessly integrate new features and updates.
The benefits of API testing are manifold, ranging from improved test coverage to cost-effectiveness. By leveraging automation in API testing, organizations can unlock additional advantages such as streamlining processes, accelerating time-to-market, and optimizing resource utilization.
Let’s explore the benefits of API testing automation in detail and how it empowers businesses to deliver robust, high-performing APIs in today’s dynamic digital landscape:
Improved Test Coverage API testing automation enables comprehensive test coverage by validating the entire spectrum of API functionalities. This includes different endpoints, request methods, input parameters, and response codes. By thoroughly testing various scenarios and edge cases, testers can uncover potential vulnerabilities. They can also ensure that APIs meet all specified requirements.
Enhanced Scalability As businesses scale and evolve, their APIs must accommodate increasing loads and user demands without compromising performance. API testing automation allows teams to simulate heavy user traffic, stress test APIs under various load conditions, and identify potential bottlenecks or scalability issues. By proactively addressing scalability concerns, organizations can ensure seamless user experiences and prevent service disruptions.
Faster Time to Market API testing automation accelerates the software development lifecycle by streamlining testing processes and reducing time to market. Automated tests can be executed quickly and repeatedly. This allows teams to detect and address issues early in the development phase. With rapid feedback loops and continuous integration pipelines, organizations can iterate faster, release updates more frequently, and stay ahead of competitors in today’s fast-paced digital landscape.
Regression Testing Changes or updates to an API can inadvertently introduce regressions, causing previously functional features to break. API testing automation enables efficient regression testing by automatically retesting existing functionalities after each code change or deployment. By detecting regressions early and automatically validating critical functionalities, teams can maintain product stability and prevent service disruptions in production environments.
Early Bug Identification and Bug Fixing API testing automation helps identify bugs and issues early in the development lifecycle, reducing the time and effort required for bug fixing. By detecting and addressing issues at an early stage, teams can prevent costly rework and ensure higher product quality. Automated tests provide actionable insights into the root causes of failures, enabling developers to troubleshoot and resolve issues promptly.
Cost Efficiency API testing automation offers significant cost savings for organizations by automating repetitive testing tasks and reducing manual intervention. Automated tests can be executed round-the-clock, maximizing resource utilization and minimizing testing overheads. Additionally, early bug detection and streamlined processes result in lower development costs and faster time-to-market, ultimately driving greater ROI for businesses.
Conclusion Incorporating API testing into your development process is not just about catching bugs; it’s about ensuring that your API platforms are reliable, secure, and performant. By prioritizing API testing, you can build trust with your users, drive innovation, and stay ahead of the competition in today’s interconnected world.
API testing automation offers many advantages for organizations that deliver robust, scalable, and high-performance APIs. From improved test coverage and enhanced scalability to faster time-to-market and cost efficiency, the benefits of API testing automation are undeniable. By embracing automation and leveraging the right tools and frameworks, businesses can ensure the reliability, efficiency, and security of their APIs. This, in turn, can enhance customer experiences and drive competitive advantage in today’s digital economy.
So, embrace API testing as a fundamental aspect of your development workflow, and reap the benefits of robust and reliable API platforms that empower your business.
Check out our platform QAPi, an AI-first API testing automation platform for the public. It’s the only free platform (unlimited time) that includes more than enough features to run your API tests with speed and efficiency.
Hello, testing aficionados! Welcome to Feature Friday, where we’re about to uncover the magic of Qyrus’ TestPilot with Dan and Linto leading the way. Imagine having a copilot or plugin tester for your testing adventures, one that not only helps you with test building and creation but also executes them with AI-driven precision. As we dive into the depths of this ChatGPT plugin for test automation, get ready for a journey filled with simplified testing processes and increased productivity!
Tell us more about TestPilot and what it exactly is.
Dan: TestPilot is one of the newest tools in Qyrus’ AI arsenal that is chat-integrated, and AI-driven, and can help you with the creation of test scenarios, the execution of Qyrus test scripts, and much more. Use this test pilot to help with testing web apps.
Linto: You can almost think of this as a ChatGPT plugin for test automation. In that way, we here at Qyrus are riding the wave in that essence and looking to make testing easier with this plugin tester. Just like things like coding, copilots have helped bridge the gap in terms of knowledge and expertise.
So, a ChatGPT plugin for test automation. ChatGPT seems to be everywhere nowadays. Even more traditional helper chatbots that you might find are now starting to be powered by ChatGPT for better results.
What is TestPilot’s overall impact on the testing process?
Dan: TestPilot will see the most impact on the test-building portion of the testing process. Although we did mention it can execute tests and give you reports back, executing tests and viewing reports is the lesser part of what this feature can do.
Linto: It’ll bring a higher degree of test coverage by enabling users to generate scenarios with simple chat prompts. Testing web apps on Qyrus is already easy but being able to take out more of the overhead of doing things like generating test scenarios can be extremely valuable in terms of effort reduction, as well. Offloading tasks that take a lot of time and manpower will snowball to show an increase in productivity.
These AI-driven tools are starting to make an impact across nearly every industry, especially in tech. We have seen it help beginner programmers to fast-track themselves to becoming more experienced and knowledgeable developers.
How might TestPilot help testers, developers, and business technologists? What value can this feature bring?
Linto: The name is in the pudding, TestPilot is meant to make the lives of testers easier. But more importantly, it’s there to help uplift those less technical members of our teams and empower them to do things like generate test scenarios, build out test scripts, and execute those all from a tool that is like a ChatGPT plugin for test automation. Business technologists would find this tool extremely useful. Developers would also be able to quickly build out and execute unit tests from the TestPilot, as well.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Dan: A lot of testing tools out there are trying to come out with their own version of a testing copilot or ChatGPT plugin for test automation. A lot of these features are brand new and for the most part under wraps, but TestPilot is ready to boost your testing today, right away!
Linto: When it comes to traditional automation testing, Qyrus in and of itself is leaps and bounds ahead because of its no-code and low-code nature. This part of Qyrus makes testing more accessible and easier than having to create complex automation frameworks that require a considerable amount of coding knowledge.
Our goal at Qyrus is to make testing easier, faster, smarter, and more scalable. With TestPilot, we can help testers achieve all of those goals in their daily tasks.
How do you see this feature impacting day-to-day operations across organizations?
Linto: TestPilot provides instant results and real-time execution. Furthermore, it can help streamline processes and ensure a greater amount of test coverage. It can identify critical functionalities of the application and generate scenarios accordingly.
Dan: Test automation, Qyrus, and TestPilot all look to reduce the amount of human error that might present itself during testing. With manual testing, the chance for human error is greater than automation. However, with things like TestPilot, you can eliminate the risk of missing important test scenarios.
What might we see in the future in terms of updates for TestPilot?
Linto: Like any ChatGPT plugin for test automation, the goal is to improve the correctness of the artifact generation. More specifically, we hope to generate better test scenarios and test scripts. Also, we will most likely be expanding TestPilot to other services in the future, as well.
And with that, we wrap up our dive into the innovative world of TestPilot. Dan and Linto have shown us how this tool isn’t just a ChatGPT plugin for test automation; it’s a game-changer for both testers and non-testers and tech-savvy and non-tech-savvy individuals alike. With easier test scenario generation, real-time execution, and a sprinkle of AI magic, Qyrus’ Test Pilot is set to streamline testing processes across organizations. So, here’s to faster, smarter, and more efficient testing with TestPilot. Until next time, happy testing!
In today’s digital age, the Financial Technology (Fintech) industry has evolved how we handle financial transactions, offering convenience, efficiency, and accessibility. Experts estimate the Global Fintech Market size to be USD 312.92 billion in 2024 and project it to reach USD 608.35 billion by 2029.
However, with the rise of Financial Technology comes the pressing need for robust security measures and stringent regulatory compliance. This is to safeguard sensitive financial data and maintain trust among users. In this blog, we will explore how test automation helps ensure security and compliance in the Fintech industry.
Introduction Financial Technology, or Fintech, encompasses a wide range of technological innovations aimed at enhancing financial services. Financial technology solutions have disrupted traditional banking and financial sectors, offering seamless experiences to consumers and businesses alike. However, with these advancements come inherent security risks and regulatory challenges that must be addressed to uphold the integrity of the financial ecosystem.
Importance of Security and Compliance in Fintech Fintech, encompassing a wide array of financial services delivered through technology, relies heavily on trust. Users entrust their sensitive financial information to Fintech apps and software, expecting robust security measures to safeguard their data. Ensuring security and compliance is not just a regulatory requirement but a fundamental necessity for the credibility and sustainability of any Fintech venture.
Did you know that the average Spending per employee in the cybersecurity market is projected to reach US$52.21 this year? Security breaches in Fintech can have severe repercussions, damaging the company’s reputation and the users’ trust.
Hence, incorporating stringent security measures is imperative. From encryption protocols to secure authentication methods, every aspect of Fintech software must be fortified against potential threats.
Moreover, with the increasing prevalence of cyberattacks targeting the financial sector, staying ahead of the curve is essential. Regular security audits and proactive measures are necessary to safeguard against evolving threats.
Similarly, compliance with regulatory standards is non-negotiable in the realm of Fintech. The financial industry is heavily regulated, with stringent requirements imposed to protect consumers and maintain the financial system’s integrity. Failing to adhere to these regulations can lead to severe penalties and legal consequences. Therefore, Fintech companies must not only stay abreast of the latest regulatory developments but also ensure full compliance in their operations.
Security Threats: Fintech apps and software are vulnerable to various cyber threats, such as phishing attacks, malware, ransomware, and data breaches. These threats can result in financial losses, reputational damage, and legal consequences for Fintech companies.
Data Protection Regulations: Compliance with data protection regulations such as GDPR and CCPA presents a significant challenge for fintech companies. Ensuring that customer data is collected, processed, and stored securely while adhering to regulatory requirements demands robust data governance practices and often necessitates substantial investments in compliance measures.
Risk of Financial Fraud: Fintech apps and software are prime targets for financial fraud due to the large volume of transactions and the interconnected nature of digital financial systems. Fraudulent activities such as identity theft, account takeover, and payment fraud pose a considerable threat to both consumers and financial institutions, requiring advanced fraud detection and prevention mechanisms.
Complex Regulatory Landscape: The fintech industry operates within a complex regulatory landscape characterized by varying regulations across different jurisdictions. Compliance with securities regulations in banking, anti-money laundering (AML) laws, and know-your-customer (KYC) requirements presents a formidable challenge for fintech companies seeking to expand their operations globally.
Third-party Risks: Fintech companies often rely on third-party service providers for various functions, including cloud hosting, payment processing, and customer support. However, outsourcing certain aspects of operations introduces additional security and compliance risks.
The Need of the Hour: Test Automation The automation testing market is projected to be USD 55.2 billion by 2028. Selecting the right automation strategy is key to being effective and efficient in being compliant with security regulations in the Fintech world
Test automation involves using software tools to execute pre-scripted tests on Fintech applications and software. By automating the testing process, Fintech companies can efficiently identify vulnerabilities and ensure that their fintech software meets regulatory requirements.
Test automation plays a crucial role in addressing security concerns and compliance requirements in the Fintech industry:
Regression Testing: Test automation streamlines regression testing, allowing Fintech companies to verify that software updates and changes do not introduce new security vulnerabilities or compliance issues.
Risk Mitigation: By leveraging test automation, Fintech companies can proactively mitigate risks associated with security breaches and non-compliance. Regular automated tests help identify and rectify vulnerabilities before they can be exploited by malicious actors, thereby safeguarding the integrity and reputation of Fintech firms. Quick Read: How CIOs can improve Speed, Security and Quality in Testing?
Competitive Advantage: Fintech firms that prioritize test automation gain a competitive advantage by demonstrating a commitment to security and compliance. This fosters trust among customers and partners, leading to an increase in the adoption of Fintech software.
Cost-Efficiency: Although initial implementation may require investment, test automation ultimately proves cost-efficient by reducing the likelihood of security breaches and non-compliance incidents. By preemptively addressing security concerns through automation, Fintech companies can avoid costly repercussions associated with data breaches, regulatory fines, and reputational damage. The average savings for organizations that use security AI and automation extensively is USD 1.76 million compared to organizations that don’t. Quick Read: Cut Costs with AI & Machine Learning in Software Testing
Scalability and Flexibility: Test automation offers scalability and flexibility, allowing Fintech companies to adapt to evolving security threats and regulatory requirements. Automated tests can be easily scaled up or modified to accommodate changes in the Fintech landscape. This ensures the security measures and compliance protocols are robust and up-to-date. Some Great Practices Fintech Companies Should Adhere To! To maximize the benefits of test automation in the Fintech industry, Fintech companies should adhere to the following best practices:
Establishing a Comprehensive Test Automation Strategy: Fintech companies should develop a comprehensive test automation strategy that aligns with their business objectives, security requirements, and compliance goals. The strategy should encompass test planning, tool selection, test case design, and execution.
Integration with DevOps Practices: Test automation should be integrated into the DevOps pipeline to enable continuous testing and delivery of Fintech applications and software. By automating testing within the CI/CD workflow, Fintech companies can detect and address security vulnerabilities and compliance issues early in the development lifecycle.
Leveraging AI/ML for Advanced Testing: Fintech companies can leverage AI/ML platforms like Qyrus to enhance test automation capabilities, such as predictive analytics, anomaly detection, and intelligent test generation. These advanced testing techniques enable Fintech companies to identify emerging security threats and compliance risks proactively.
Conclusion Given the sensitive nature of financial data and transactions, security and compliance are paramount in the Fintech industry. As per IBM’s Cost of a Data Breach Report 2023, the global average cost of a data breach in 2023 was USD 4.45 million, a 15% increase over 3 years.
Test automation plays a critical role in addressing security concerns and compliance requirements. It provides comprehensive test coverage, ensuring thorough examination of all aspects of the Fintech application. Moreover, automation enables faster testing cycles, facilitating the rapid detection and resolution of issues. This agility is crucial in the fast-paced world of Fintech, where timely updates and releases are essential to staying competitive.
Attention, fellow testers! Prepare to embark on a journey into the realm of Qyrus’ Data Amplifier, where Tim and Adhi are your guides to this fantastical tool. Picture this: it’s as if you have a digital alchemist right at your fingertips, crafting realistic yet synthetic data to turbocharge your testing adventures. With the Data Amplifier, testing becomes less of a chore and more of a magical experience. So, fasten your seatbelts, because we’re about to delve into the enchanting world of how we amplify data. Ready to witness testing transform into a magical journey? Let’s dive in!
Tell us more about the Data Amplifier tool and its use cases.
Tim: The data amplifier tool goes beyond just synthetically generating data, it can take in the data that you provide to it and use that as a foundation to then amplify data for your testing needs. This is realistic yet synthetic data.
Adhi: One key use case is web form testing in web application automated testing. We can automatically generate and populate data for web forms to test things like validations, error messages, and database insertions. We can also handle the parameterizing of API endpoints during testing. Furthermore, we can ensure consistent data formats to help test how endpoints handle different data inputs.
Tim: Another use case to point out is performance testing, where we can use amplified data to simulate real-world usage and test software under various data loads. The last thing to point out is also security testing where we can generate data with potential security threats like SQL injections to ensure software robustness.
Now that we’ve uncovered the versatile use cases of the Data Amplifier tool, let’s zoom out and examine its broader impact on the testing process. Let’s delve in!
What is the overall impact Data Amplifier might have on the testing process?
Adhi: Data Amplifier can help improve efficiency by helping to reduce manual effort in data preparation and let testers focus more on actual testing. Furthermore, using it to amplify data ensures reliability, as we just mentioned because we can use it to test our software against consistently structured data.
Tim: On top of that, this tool helps with scalability. This allows testers to use it for both small and large projects, and small applications or enterprise-level systems. Lastly, it’ll provide comprehensive testing because of its capability to generate a variety of data. This makes sure that you’ve explored every avenue and covered every test case or scenario in the data you provide in the test.
How might this tool help testers, developers, and business technologists? What value can this feature bring?
Tim: This tool helps testers to quickly and efficiently parameterize their test for data-driven testing and with consistent data formats. For testers, instead of having to manually create this data or have some 3rd party tool to generate or amplify data, this tool comes packaged with the Qyrus platform. Testers can easily amplify data and use it directly within the Qyrus platform on their tests without any integrations needed from their end. What’s also awesome is that developers can amplify data for their unit tests if needed, as well.
Adhi: Beyond that, it’s super easy to amplify data. Business technologists would find it extremely simple to amplify data themselves. They can do all of this data amplification in just a short few minutes, making something that would have traditionally been really complex and very clear-cut.
Now that we’ve seen how the Data Amplifier can turn testing tasks from headaches into joyrides, let’s take a peek at the competition. Are there other tools out there performing magic tricks like ours, or are they still stuck in the Stone Age of manual data handling?
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Adhi: Other tools out there can perform this task for developers out there. Doing it all manually on their own would be the most time-consuming, but utilizing tools makes things much quicker. The real value that comes from our data amplification tool is that it comes with Qyrus and testers can make use of it right away and very easily within the platform.
With how easy this tool makes handling this data, we are sure to see making the everyday lives and chores of testers easier. Tim’s going to give us a sneak peek into the future, where testers’ lives are filled with a little more ease and a lot less manual data input. Let’s dive in!
How do you see Data Amplifier impacting day-to-day operations across organizations?
Tim: Overall, a lot of time would be saved on the tester’s end. Some out there still manually input all of this data for their testing, especially those that have not yet even dipped their toes into the automation software testing realm. Some of this can then even be offloaded to other members of the team, who might even be less technical.
As we wrap up this journey through the world of Qyrus’ Data Amplifier, one thing is clear: testing just got a lot easier. Tim and Adhi have highlighted the tool’s versatility, efficiency, and simplicity, making it a must-have for any testing arsenal. So, get ready to amplify your testing with Qyrus! Until next time, happy testing!
Greetings, testing enthusiasts! Today, we’re turning our attention to the power of CSS selectors, with Amy and Jorell leading the way. They aren’t just patterns; they’re the secret sauce that allows us to target and style HTML elements like never before. Buckle up, because we’re about to take a wild ride through the world of CSS magic!
What are selectors in CSS?
Amy: CSS selectors are patterns that match HTML elements based on their attributes, types, classes, IDs, states, or relationships and are used to apply styles to selected elements or with JavaScript. They can be used to select an element by its tag name or even an element based on its position in the DOM.
Jorell: Some examples are element, class, ID, attribute, pseudo-class, pseudo-element, and combinatory selectors. All of these can be combined to even form more specific or complex selectors.
Tell us more about how Qyrus can use CSS selectors when identifying elements.
Jorell: Well, with Qyrus, we enable users to utilize CSS element selectors to identify HTML elements. This is something we can do rather than use XPaths or other locators that can also be dynamic in nature, making automation a bit trickier. We can use CSS selectors to identify the changing attributes of elements like color changes or changes in states, like hovering over elements for example. Users can verify the style changes of their elements in that manner.
Amy: One example use case would be when clicking on a hyperlink on a website, the color of the hyperlink changes shades. Another example would be verifying the color change of a button when hovering over it. And lastly, a tester could verify the style value to see if something like a button is enabled.
Jorell: We find that overall we find a reduced amount of effort when it comes to maintaining test scripts due to the fact that using CSS element selectors might be a bit more reliable when it comes to certain cases. As stated before, some locators can be dynamic, like identifiers and classes. Furthermore, due to updates to the application and changes made on the webpage, XPaths might even break.
Amy: In a way that also ensures more reliable test executions due to less maintenance required and less downtime due to the maintenance.
How might utilizing CSS selectors help testers, developers, and business technologists?
Amy: Testers can have more options to verify elements. The typical way that most do this through is through IDs, XPaths, and classes. This can even in a way lead to less friction between the testers and developers, as there might be less back and forth between when it comes to utilizing dynamic locators or providing stable and static locators that the testers can make use of when automating.
Jorell: Due to their nature and naming conventions, it can be easier for those less tech-savvy users like business technologists and analysts to read and understand what’s happening in the test script and execution. Rather than being confused by weird-looking XPaths, these users have a better grasp of what’s going on at hand.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Jorell: Some competitors don’t make use of them when it comes to automation. Qyrus has it as an option out of the box and from the start.
Amy: Automation is possible without using them, for sure. However, the problem there is that utilizing them makes it easier to verify what you specifically are looking for, like the specific color an element might have changed to.
As we wrap up this adventure into the realm of CSS selectors, one thing is clear: Qyrus is paving the way for efficient and reliable testing practices. Amy and Jorell have showcased how CSS selectors not only make testers’ lives easier but also bridge the gap between tech-savvy developers and less technically-inclined business technologists. So next time you’re faced with verifying style changes or handling dynamic elements, remember the magic of CSS selectors. Until next time, happy styling and testing!
Hey there, curious minds! Ever heard of Qyrus’ API Builder? Let Tim and Adhi from the Qyrus team fill you in! It’s like having your own personal API magician! Just give it a description of the APIs you need to have mocked, and voila! It cooks up APIs faster than you can say “testing!” This tool is a game-changer for testers, saving precious time and effort. So, grab a coffee, sit back, and let Qyrus’ AI-powered API Builder do the heavy lifting for you!
Tell us more about API Builder offered by Qyrus and its use cases
Tim: Qyrus’ API Builder tool is a single-use agent (SUA) that we have developed to aid users when they want to mock or virtualize APIs for their testing purposes. With this SUA, we are able to provide a description of what kind of APIs we want mocked. The tool itself analyzes what we’ve input and, from there, will do the job for the user.
Adhi: A user can put in something like “e-commerce store selling used and refurbished iOS and Android mobile devices” We would get back a list of APIs in both the Swagger JSON format as well as visually being able to see the API definitions. The user can then choose to download this and then upload it to the Qyrus platform in the Service Virtualization service.
Now that we’ve uncovered the inner workings of API building on Qyrus, let’s shift gears and explore its impact on the testing process. Tim and Adhi reveal how this innovative tool is revolutionizing API mocking, making it faster and easier than ever before.
What is this feature’s overall impact on the testing process?
Tim: The biggest benefit of this feature has to be with regard to how quickly it can build out these APIs for users to then mock on the Qyrus platform. Mocking APIs can be a tedious task in and of itself, and Qyrus already makes it easier for the user to mock these by themselves using the platform. However, we recognized that there can be an even quicker and easier way to do this, utilizing generative AI in the process. By just providing a description, our SUA can do all the heavy lifting while you can go get a coffee.
Adhi: As we’re all aware, generative AI is making headway in virtually every field. With AI assistants at our doorstep and SUAs being developed left, right, and center to handle various tasks, Qyrus is stepping up to the AI plate itself and pushing its AI features even further and to the max. Be prepared to hear more from us on the AI front in the coming months.
We’ve explored how Qyrus’ API Builder is streamlining API mocking with generative AI, now let’s delve into how this feature can benefit testers, developers, and business technologists. Adhi and Tim shed light on the value this tool brings to different roles within organizations, from accelerating testing processes to simplifying API virtualization.
How might building an API on Qyrus help testers, developers, and business technologists? What value can this feature bring?
Adhi: This is primarily a tool meant to be used by testers. During the testing process, sometimes certain APIs might not be finished with development, causing hold-ups and delays. These hold-ups and delays can sometimes be costly. The goal of Qyrus and this tool is to help you bypass that issue entirely. Testers can now quickly and easily virtualize these APIs and get on moving forward in the testing process with no hold-up or delay.
Tim: Furthermore, business analysts can also virtualize these APIs themselves because of how easy it is. They themselves can just as simply enter a description of the API or APIs that they want to mock, and it’ll soon appear right in front of them. And another thing to mention is that if any APIs that are part of the testing process happen to belong to a 3rd party, we can mock those as well to help avoid extra costs and hassle.
Before we delve into the impact of Qyrus’ API Builder on day-to-day operations, let’s take a moment to explore the competitive landscape. Tim and Adhi shed light on the existing alternatives and how Qyrus stands out among the competition with its seamless integration, generative AI, and user-friendly approach to API mocking and building an API.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Tim: There definitely are similar tools out there that can help assist users with building out and mocking APIs, but none are as seamless as the one you experience here on Qyrus. Everything with Qyrus is connected and intertwined. Easily generate these APIs, import them onto the platform, and watch them go live within minutes.
Adhi: Without Qyrus, users would have to find a similar tool out there to mock these APIs. There are plenty of them out there, some free, and some not, and all of them are missing the fact that they are built with a testing platform attached and some do not utilize generative AI but rather require the user to provide all configurations and specifics.
How do you see this feature impacting day-to-day operations across organizations?
Tim: The biggest difference in terms of day-to-day would be the amount of time that we save users when it comes to, again, creating and mocking these APIs. This would free their time up to handle other important tasks. Not all testers and developers are created equal, and of course, that’s okay, but to some, this task might take much longer when compared to other individuals. Complexity always plays a role, but with Qyrus’ API Builder that complexity is taken out of the equation, and the time differential is also removed. When it comes to API building, Qyrus takes the cake in terms of easiness and simplicity. It’s so easy, an intern can do it.
So, there you have it, folks! Qyrus’ API Builder is your new best friend in the testing world. Adhi and Tim have shown us the magic of quick-and-easy API mocking. As we dive deeper into the AI-driven testing era, Qyrus is the place to be for all your testing needs. This tool is a game-changer, empowering testers, developers, and business technologists to work smarter, not harder. Stay tuned for more API adventures from Qyrus!
Dive into the magic of effortless test integration with Qyrus’ AI-powered test converter! Picture this: Ananya spills the beans on Qyrus, where importing scripts is as breezy as a stroll in the park—no need to endure the painstaking task of rebuilding extensive test suites. Tim chips in to cheerlead this digital superhero, especially for those script-wranglers dealing with a multitude of codes. Say goodbye to script-creating marathons; Qyrus is here to save the day, potentially freeing up hours, or even days, of your precious time!
Tell us more about Qyrus’ AI-powered test converter and what it can do.
Ananya: Qyrus allows users to take scripts that they have created outside of Qyrus, convert them, and upload them directly into Qyrus. This allows users to not have to recreate the same tests again from scratch and eliminates the tedious work that comes with it.
Tim: This targets users who may have been using other methods of testing applications. Especially if a user has many and/or long scripts, one could save hours, even days, or tedious work trying to get their working tests integrated into Qyrus.
Discover the transformative impact of the test converter on the testing process. Ananya emphasizes a paradigm shift in the test-building phase. Instead of starting anew, users can convert existing Selenium scripts seamlessly into Qyrus-compatible ones, preserving their hard work while adopting an enhanced testing approach.
What is the test converter’s overall impact on the testing process?
Ananya: The converter introduces a significant shift, particularly in the test-building phase of the process. Instead of requiring users to start from scratch and recreate their scripts, they now have the valuable capability to convert their already existing scripts into Qyrus-compatible ones. This addresses a common concern we’ve encountered in the past – the dilemma of leveraging existing Selenium scripts that are already in use. It’s a practical solution that allows users to preserve their hard work while adopting a new and improved approach.
Can you elaborate on the compatibility of the test converter with different open-source tools?
Tim: Absolutely. The converter extends its reach to all open-source tools whose code is written in popular languages like JS, TS, Java, C#, and Python. This broad compatibility ensures that users working with a diverse range of open-source testing tools can seamlessly transition and utilize Qyrus, adding a layer of versatility to the testing process.
How might these test converters help testers, developers, and business technologists? What value can this feature bring?
Ananya: This tool is primarily aimed at testers, offering a significant advantage in terms of efficiency and reusability. Testers no longer find themselves repeating the laborious task of recreating scripts that were previously built on other open-source tools. With the Qyrus Test Converter, testers simply upload their existing test scripts, and the converter seamlessly handles the code translation, generating a JSON file for the user. Subsequently, the user can effortlessly upload the file into any test in Qyrus, and the steps will automatically appear, streamlining the entire process.
Tim: Business technologists stand to greatly benefit from this feature as well. While Qyrus prides itself on being a no-code and low-code platform with user-friendly features for building test scenarios, some business technologists may lack the technical expertise to handle more advanced test scripts. With the converter, a technologist can easily convert and upload tests. From there, they can verify if the tests meet all the set criteria without grappling with complex technical details. This accessibility extends to developers as well, providing a user-friendly bridge for those more technically inclined.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Ananya: While some competitors do offer resources to assist in integrating previous tests onto their platforms, not all provide the convenience of an automated test converter. Qyrus stands out by offering a dedicated test converter, streamlining the process of building the bulk of scripts. Moreover, if any adjustments are required, the Qyrus team is readily available to provide support in editing these tests, ensuring a seamless transition.
Can you elaborate on the benefits of having a test converter, especially in comparison to other testing tools?
Tim: Opting for a more conventional approach, without the aid of testing tools, leaves a tester with limited options. They might find themselves subscribing to a tool that lacks the essential feature of a test converter, leading to inefficiencies and additional challenges. Alternatively, they could persist with building automated or manual tests manually, a time-consuming endeavor that demands substantial resources. Qyrus’ test converter not only offers a more efficient and automated solution but also presents a cost-effective and time-saving alternative, contributing to the overall benefits of translation in the testing process.
Delve into the benefits of the Qyrus test converter compared to conventional testing approaches. Tim explains how the test converter provides an efficient, automated, and cost-effective solution, saving time and resources. It eliminates the limitations faced by testers subscribing to tools lacking a test converter and those manually building tests, presenting a smarter alternative for testing processes.
How do you see the test converter impacting day-to-day operations across organizations?
Ananya: The impact of the test converter on day-to-day operations is quite substantial. Not only does it eliminate the cumbersome task of rebuilding scripts from scratch, but it also opens up opportunities for users to build upon these scripts using the clone script method in Qyrus. This streamlined approach simplifies the testing process, allowing users to focus on refining their tests rather than investing time in recreating them.
Tim: The test converter significantly contributes to saving effort and optimizing testing operations within organizations. It eliminates the need for duplicating tests created on legacy platforms, enabling users to seamlessly transition and leverage the unique features of the Qyrus platform. This not only enhances efficiency but also provides the freedom to think of smarter ways to test applications, rather than being tied down to the repetitive task of script building. The ability to upload a script and then clone it as many times as needed, building different scenarios based on the previous script using Qyrus’ clone script method, further exemplifies the benefits of translation in testing processes.
What kind of updates might we expect to the test converter in the future?
Ananya: The Qyrus test converter has been tailored to cater to users from both automated and manual testing backgrounds, making significant strides in code translation. Currently, it supports the conversion of manual codebases, including GDD, Gherkins, and Glue, as well as those from Selenium. Building upon this foundation, we recently introduced the capability to convert individual tests and POM-based tests using the test converter. Looking ahead, Qyrus aims to further expand the range of supported test types, providing users with even more options for seamless code translation.
Experience a testing revolution with Qyrus’ test converter—an innovative tool designed to streamline integration, enhance efficiency, and unlock new possibilities in the dynamic field of test automation. As Qyrus evolves, so does its commitment to providing users with cutting-edge solutions, making the testing process more accessible and effective.
Welcome to a Feature Friday spotlight on Qyrus, where precision meets patience in the world of testing. Today, we unravel the intricacies of Qyrus’ wait action types, a game-changer in the realm of action-based testing. These aren’t just any waits; they are the conductors orchestrating a harmonious testing symphony. Join us as we explore how Qyrus tackles the challenge of variable wait times, making testing more adaptive and robust.
Tell us more about the different “Wait” action types on Qyrus.
Ananya: Qyrus provides users with the ability to incorporate a wait action within their test cases, particularly useful when an element or web page requires some time to appear. Users can simply specify the desired wait duration in seconds, allowing the script to adapt accordingly. However, what if the wait times for certain elements vary significantly? What if certain elements take less time to appear in certain runs, yet the overall script execution still takes a considerable amount of time? Qyrus addresses this by offering wait action types that go beyond simple time-based waits.
Tim: These wait actions are designed to specifically target elements that may have variable wait times for appearance or interaction. External factors, such as a website’s API calls or a user’s bandwidth, can influence the test time for a script. Instead of relying on a fixed time to wait for an element, Qyrus provides the flexibility to wait until that specific element is available. This approach ensures a more adaptive and accurate synchronization with the varying conditions, contributing to a more robust and reliable testing process.
Now, as we paddle down the stream of Qyrus’ intricate testing waters, it’s worth pausing to marvel at the genius behind its action types. It’s like having a toolkit where you pick the right tool for the job, making test script creation a breeze. Just select the action type that fits your testing needs, fill in the blanks, and voilà – your script is ready to roll. It’s like the ‘easy button’ for testers!
What might be the overall impact these action types can have on the testing process?
Ananya: Qyrus adopts an action-based testing design, providing users with a versatile selection of action types available in a kind of library. Users can choose an action type that aligns with their testing needs. Once that’s decided, it’s a matter of filling in the necessary information for that specific action and incorporating it into the script. It’s a streamlined process that allows users to easily construct and customize their test scripts based on the required action type and steps.
Tim: That being said, Qyrus is made to make testing more efficient, and that comes in more ways than just one. Our action-based testing methodology basically does more than half the work for you. All that’s left is giving things like element locator values and required data for input where necessary. On top of that, make use of Qyrus’ various recorders, like the web or mobile recorder, to speed processes up and keep things rolling.
How might these wait actions help testers, developers, and business technologists? What value can this feature bring?
Ananya: Testers, in the realm of action-based testing, find significant advantages with these wait actions. This feature not only saves them time but also contributes to more informed test schedules. By eliminating the guesswork surrounding the duration of a page or element change, testers can efficiently streamline their testing processes, minimizing the reliance on trial and error.
Tim: Developers, within the framework of action-based testing, value this feature for ensuring the appropriate time intervals for elements to appear during testing. Identifying and addressing time lags at an early stage markedly enhances the efficiency of the development process. Furthermore, business technologists can leverage these wait actions to verify the correct elements’ appearance on the webpage, aligning with the principles of action-based testing and providing a thorough understanding of the application’s behavior.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Ananya: When it comes to addressing this particular problem, it varies among competitors. Qyrus sets itself apart by integrating with a wide range of attributes, including XPaths, IDs, names, and more. This extensive coverage is not universal among competitors, and some may lack the flexibility to handle a diverse set of attributes. This distinction becomes crucial because, in certain cases, competitors might face issues like a “Wait for Element” step breaking due to limited attribute coverage. Qyrus, on the other hand, ensures comprehensive coverage, whether dealing with static or dynamic attributes.
Tim: Qyrus brings a unique advantage to testers by allowing them to wait for the appropriate duration, especially when dealing with elements that are more unstable or dynamic. In the past, testers might have encountered challenges with faulty locators. Qyrus’ extensive coverage becomes particularly valuable in such scenarios, offering the capability to pinpoint a working locator value. This distinction can significantly enhance the reliability and effectiveness of the testing process, addressing challenges that testers may have faced with competitors lacking similar comprehensive coverage.
How do you see these impacting day-to-day operations across organizations?
Ananya: From a testing perspective, these features are transformative. Testers can now operate with more precision, eliminating the guesswork around how long a page or element change might take. This reduction in uncertainty leads to a substantial decrease in the need for trial and error. Testers no longer have to wait for the longest possible duration; instead, they can wait until the element is ready for interaction, optimizing the testing process.
Tim: Qyrus is taking action-based testing to the next level. The impact of these features extends to the precision of test-building scenarios and coverage. Testers can now be more accurate and specific, eliminating the need to deal with arbitrary values or gauge when an element is available. The ability to wait until the correct locator value appears, coupled with the passage of the wait time, may eliminate the need to add additional steps in scripts to verify the existence of an element. This not only streamlines the testing process but also enhances efficiency and clarity in day-to-day testing operations across organizations.
Let’s face it; testing without Qyrus’ wait actions would be like trying to solve a puzzle in the dark. Testers, developers, and business technologists alike are finding a friend in Qyrus. Testers save time and effort, developers enjoy a smoother development process, and business technologists get a front-row seat to a more informed and efficient application landscape. Qyrus – making testing a collaborative success story!
What kind of new updates can we expect from Qyrus in the future on this front?
Ananya: Looking ahead, the roadmap for this feature is quite exciting. Our focus is to target as many tricky elements as possible, ensuring that Qyrus remains at the forefront of addressing dynamic testing scenarios. Building on our commitment to action-based testing, we’ve already introduced several new wait action types, each crafted to address specific scenarios our clients have encountered. Moving forward, we are continuously exploring additional enhancements and improvements to further expand the capabilities of wait actions. Additionally, we’re exploring the potential of leveraging AI/ML to detect element or page changes, a prospect that holds promise in enhancing the adaptability and intelligence of Qyrus in handling evolving testing requirements.
As we draw the curtain on our exploration of Qyrus’ wait action types, it’s not just an end but a crescendo in the symphony of precision and efficiency. Qyrus has transformed waiting into an art, and each script becomes a masterpiece of testing ingenuity. As the spotlight dims, the impact of Qyrus’ action-based testing with versatile wait actions echoes in the corridors of testing excellence, promising a future where precision meets anticipation. This isn’t just about the wait; it’s about the orchestration of seamless, adaptive, and intelligent testing. Stay tuned as Qyrus continues to compose innovations that resonate with the ever-evolving needs of dynamic testing scenarios. The stage is set, and the best is yet to come.
Strap on your digital adventure boots and get ready for a whimsical journey into the tech wonderland with our guides, Brett and Joyal! They’re here to sprinkle a dash of magic on the latest upgrades in iOS device streaming capabilities. Picture this as an enchanted carpet ride through the realms of streaming testing and live testing, promising a seamless and reliable experience for all you daring souls testing iOS apps. Buckle up! We’re about to explore the enchanted details of these updates and uncover their playful implications for online iOS device testing. Let the digital adventure begin!
Tell us more about the new updates to iOS device streaming capabilities in the mobile testing service. Give us some insights into what kind of impact this might have.
Brett: The recent updates to iOS device streaming bring about improvements in both quality and stability. These enhancements play a significant role in test building and execution, ensuring a smoother and more reliable experience for users.
Joyal: These updates have increased the reliability of streaming testing on iOS devices. One impact is the reduction in the time testers spend building scripts, thanks to the improved capabilities. Users are finding increased efficiency, especially when leveraging other tools like the mobile recorder tool for test building. The lasting impacts downstream in the testing process are evident, making the overall testing experience more streamlined and effective.
How might these new updates help testers, developers, and business technologists? What value can this feature bring?
Brett: For testers, the value lies in utilizing this feature while building iOS tests with the live test builder. The updates ensure that they encounter fewer interruptions to the streaming testing process, contributing to a more seamless and uninterrupted test-building experience. Developers, on the other hand, benefit from a live preview of the device during test execution, including the audio from the device.
Joyal: When it comes to business technologists viewing reports of running tests, these updates offer a valuable enhancement to live and streaming testing. They can now watch the live stream preview of the test without interruptions. This capability provides business technologists with real-time insights into the test execution process, contributing to a more informed and efficient decision-making process based on the live stream preview.
Is there still more work to be done, or more updates to be made for better iOS streaming capabilities?
Brett: Absolutely. As time progresses, there will always be room for continuous improvement and updates. Currently, our focus is on deploying these enhancements to all devices across all environments. The goal is to ensure a consistently improved streaming experience for users across the board.
How do you see these updates impacting day-to-day operations across organizations?
Brett: The increased stream availability resulting from these updates has made a tangible difference in day-to-day operations. Building iOS test scripts has become notably easier and more streamlined, making the world of streaming testing that much more efficient.
Joyal: The expanded device availability not only allows for quicker test building but also contributes to a more efficient process. Additionally, the reduction in latency when building tests is another notable impact on day-to-day operations. Overall, these updates play a key role in enhancing the speed and efficiency of test building across organizations.
And there you have it, folks – the grand finale of our whimsical exploration through the enchanted forest of revamped iOS device streaming, brilliantly guided by the dynamic duo, Brett and Joyal. What a journey it’s been! The impact on streaming testing and live testing is like finding the pot of gold at the end of a digital rainbow. These updates not only sprinkle efficiency dust on test buildings but also promise a more reliable online iOS device testing experience. So, wave goodbye to glitches and hello to a future where testing iOS apps is smoother than a perfectly brewed potion. Here’s to the magical strides in stability and quality – because, in the world of live and streaming testing, the future is looking brighter than ever!
Jerin Mathew
Manager
Jerin Mathew M M is a seasoned professional currently serving as a Content Manager at Qyrus. He possesses over 10 years of experience in content writing and editing, primarily within the international business and technology sectors. Prior to his current role, he worked as a Content Manager at Tookitaki Technologies, leading corporate and marketing communications. His background includes significant tenures as a Senior Copy Editor at The Economic Times and a Correspondent for the International Business Times UK. Jerin is skilled in digital marketing trends, SEO management, and crafting analytical, research-backed content.
