Description:
In this fast-paced digital world, mobile automation has become fairly complex and laborious, especially to an untrained eye. Moreover, to maintain the competitive edge, organizations strive to achieve the best combination of speed, quality and cost to get on top.
Utilizing a codeless, automated, AI and ML driven mobile testing platform can improve mobile automation testing quality while increasing efficiency and reducing time to market.
In this testing webinar, Suraj will take you through Qyrus’ mobile testing platform in detail and talk about how automating mobile application testing provides a faster, more efficient testing process with a wider range of coverage and better test results.
How to achieve full automation – Integrations and Foundations
Mobile testing demo in detail
Speaker:
Suraj Patel, Platform and Sales Engineer, Qyrus
Speaker Bio:
A platform expert with nearly half a decade of industry experience and a specificity towards developing and maintaining automated testing frameworks, Suraj Patel focuses on understanding and optimizing unique testing requirements through automation. Commanding a background in software development with gained experience across industry leading events and conferences, Suraj is passionate about the cutting edge of development and learning how to utilize different technologies to enhance the Quality Assurance lifecycle.
As he would say, reciting a quote by Godfrey Reggio, “It is not that we use technology, we live technology” and in the same light, Suraj is empowered to bring end users the smile they deserve by promoting high quality, functional applications through optimization of testing and quality assurance practices.
As David Copperfield once said, “The magic lives in the performance!” Although we all know David Copperfield to be a magician, not a tester, the same can be said in the testing world, as well! Performance testing is such an important and integral part of testing an application. Measuring the time it takes for your webpage to load or the time it takes for some tasks to be completed is included in performance testing. However, today, we are here to talk a little bit about the performance testing of APIs. But, wait, there’s more! We’re going to be talking specifically about the performance testing of end-to-end API processes. Here to deliver more information for us today are our good friends Parth and Steve; without further ado, let’s delve in!
Tell us more about end-to-end API performance testing offered by Qyrus and its use cases.
Steve:
We have seen many people take advantage of our API Process Testing service, in which we enable users to stitch or chain together API tests in order to make a complete end-to-end flow. This gave users the kind of holistic testing they were looking for. With Qyrus, we can check the functionality of each individual API, but with this, we can also check that these APIs work together exactly as they should.
Parth:
Now, being able to test this process’ performance is a big step forward. Previously, we were able to see the basic response times for each API call in a process, but now we can get a much more granular view that we were never able to before.
Steve:
Exactly. We are, for example, able to get values back for the response time of the entire API flow, the response time per API, as well as the status code per API. This is tested over a certain thread count, or users accessing the same resource—or in this case, flow—concurrently.
Adding more tools and functionality to Qyrus is a never-ending task here. Going further into process testing, you can learn more about our individual API performance testing here from another Feature Friday. If interested, here are two more about web performance profiling and mobile performance profiling.
What is end-to-end API performance testing’s overall impact on the testing process?
Parth:
In general, the impact we see is a larger amount of test coverage. This is because the user is able to reuse these API Process tests that they created for functional purposes, but instead run them to test performance.
Steve:
Furthermore, users can now, in a literal sense, perform performance tests on these processes. Prior on Qyrus, you had to run performance tests on each functional API in order to get an idea of what the performance metrics were like. But still, you had an incomplete picture.
How might this feature help testers, developers, and business technologists? What value can this feature bring?
Parth:
Like Steve previously stated, a tester can now actually run performance tests across a whole process or end-to-end flow and can see the bigger picture, you might say.
Steve:
Beyond that, developers could test max stress levels for their APIs when they’re all connected in a flow and make adjustments from there. This can be helpful at catching performance flaws early on in the development process.
Parth:
And for business technologists, they can get better information about performance at a faster pace. These test results can be shared, emailed, or even downloaded.
Collaboration, although not an explicit feature on Qyrus, is a key quality that Qyrus upholds across the platform – whether that be collaboration during the test building phase, collaborating on test executions, or sharing reports and collaborating with other teammates that way. You can learn more about our collaborative efforts in one of our previous Feature Fridays.
How do you see this feature impacting day-to-day operations across organizations?
Steve:
Well, to start, as we mentioned before, users are now enabled to run these types of tests across entire end-to-end API flows. This would mean that day-to-day, testers no longer have to run individual process tests over and over again. Now, they can do it all from one place, and that includes functional testing, as well.
Parth:
Furthermore, no prior coding knowledge is required. It’s all been simplified down to a no-code experience where any user can understand what’s going on. As a last point, all tests here are just reused from our API Functional Testing section. Nothing has to be recreated, just reused and modified if necessary.
What might we expect to see improved about end-to-end API performance testing?
Steve:
Well, we’d like to see more performance metrics added for the user’s benefit. Things are still in progress here, and improvements never stop coming to the platform as a whole.
Parth:
Right. Some of these metrics might include ones that are currently present under our “Advanced Metrics” under API Performance Testing. This might include response latencies over time per API, hits per second, transactions per second, active threads over time, and a general summary tab where we can see max, min, and average response times and more.
If the number of features that we have across the platform isn’t magical, then I don’t know what is! Well, besides David Copperfield, Oh, and Fridays, those sure are magical! Speaking of, it must be Friday, since you’re reading this. Please have an enchanting weekend and enjoy the time off with family and loved ones. Don’t worry, though, next week we’ll pull some more fantastical features out of our hat for you to learn about! See you next week on our next iteration of Feature Friday!
There’s always room for improvement. That is true for just about everything in life, and that does not exclude testing. Innovation never sleeps, and testing has an ever-moving goalpost, so strive for continuous improvement rather than perfection. Every week, we post about some new feature or set of features that can help improve your testing in some way, and this week we are going to talk about our recent improvements to API test building on Qyrus. Joining us today are Adhiraj, Amy, and Jorell from our Chicago office to tell us more.
Tell us more about the recent updates to test building in the API solution.
Adhiraj:
The biggest update comes to our API Process Testing section. There’s a new UI update that has completely revamped how API process tests are chained together. This improves the user experience of those building these tests by making it simpler for them to see what connections are made.
Amy:
The goal of the new update was just that: to make things simpler. Instead of requiring the user to configure connections between APIs on a separate page. Users would go back and forth between two pages, and with this update, everything is done on the same page and in one place.
Jorell:
On top of that, a new navigation button has been added to aid in navigation between the different sections in API process testing. This helps reduce the number of clicks it takes to get to a certain page.
What is the overall impact these API updates have on the testing process?
Adhiraj:
Overall, these improvements help reduce the amount of time a user has to spend building these process tests. Similar to how going through a doorway and into another room can make you forget what you were going to do, the same can happen when it comes to navigating pages on a website.
Jorell:
Furthermore, these improvements can help improve test coverage through a better user experience and a reduced amount of time taken to build out a process test. That means testers can cover more at a faster pace. This also leads to a reduced amount of effort put forth to chain everything together in a large flow.
How might these API updates help testers, developers, and business technologists? What value can this feature bring?
Amy:
Well, for testers, their entire job just got easier. Making a process test is already not that difficult to do on the platform, but with these improvements and further down the line, testers should expect more smooth sailing ahead.
Adhiraj:
Because of this tool, the updates made to the test building mostly revolve around the tester, as this is a platform built just for them. However, developers can use API process testing to perform basic unit tests of the systems they build. The updates also help improve their lives when doing so.
Jorell:
In general, a business technologist would be able to better understand the connections between the APIs as well as how the data transfer is happening. Again, having to navigate from one screen to the next can be a hassle, and for less technical people, it can just make things downright hieroglyphic.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Amy:
One big differentiator from some competitors is our completely cloud-based approach. Everything can be done from a browser and from anywhere, without anything being downloaded. But to further that, the whole point of these updates is to make our test building simpler than others.
Adhiraj:
In a traditional sense, a good deal of coding knowledge would be required in order to make a process test similar to what we’ve done here. And on top of that, it’s still a hassle, unless time is taken to build out a UI for a similar system. Even then, the time and resources put in just about outweigh the benefits coming out. Maintenance and upkeep are another problem, then.
How do you see these improvements impacting day-to-day operations across organizations?
Jorell:
Keeping testers on one page, easier navigation, better connections for better understanding, and reusability are some things that will impact a user’s day-to-day when using this platform, specifically the API section.
Amy:
Well, simply put, making the whole process a degree easier. Less time and effort means higher productivity and happier workers.
Adhiraj:
And on top of all that, there are about another 10 or so features that build off this one, taking things to another level with each one, making things even faster and more efficient. And we here at Qyrus never stop coming with more.
Improvement: whether that be faster executions, more robust reporting, or better test building, Qyrus is here to improve it all. API process testing is just one stop on our route to improving the overall user experience here on Qyrus. Besides just improving the user experience, we’re doing so much more! Come on and sign up for a Free Trial to see for yourself. Join us next week to learn about more improvements to be made in your testing ecosystem!
The holiday rush is officially over! With this holiday season now in the rearview mirror, it’s time to look forward to the road ahead and get prepared for an undoubtedly busy 2023. But don’t worry, Qyrus isn’t throwing on the breaks anytime soon when it comes to features! This week, we are joined by Daniel and Joyal from our Chicago Qyrus team to learn more about some new mobile native locator strategies that have been introduced to the Qyrus platform. Without further delay, let’s race into this topic!
Tell us more about this capability offered by Qyrus and its use cases.
Daniel:
Qyrus mobile testing now has support for 3 native locator strategies when users are building out their test scripts. There are two that are supported for iOS—class chain and predicate string—and one for Android: UIAutomator.
Joyal:
This is helpful for those mobile testers who are more experienced. Native locators can speed up test executions by improving the performance of locating the element. There are elements out there that cannot be found by using ID, name, accessibility ID, or XPath locator types.
Daniel:
Even though this strategy is the most common out there and platform-agnostic—that is to say, it works for both iOS and Android devices—it can be the most time-intensive choice. By choosing a native locator strategy, a tester can leverage the flexibility that an XPath can provide without incurring a performance penalty.
For the reader’s benefit, we have provided an example below:
Example of XPath on iOS: //XCUIElementTypeOther[@label=’login’)]
As a class chain, this XPath can look like this: **/XCUIElementTypeOther[label matches “login”]
But using a predicate string, it could look like this: label matches “login”
What is the overall impact this might have on the testing process?
Daniel:
We can see this having an impact during the test-building phase when users are creating and building up their catalog or suite of test scripts for execution. This can help expedite the test-building process since, to an experienced mobile tester, using something like a predicate string is much quicker than having to get an XPath for every element.
Joyal:
Not only that, but since we see faster run times, we can say there’s a definite impact on test executions. The new native locator strategies provide an overall speed boost to the testing process as a whole.
Qyrus is always looking to push the limit when it comes to developing new tools and strategies to help enable better testing across the board for everyone involved. This is not limited to different levels or types of testers, but also to less technical personnel.
How might these new native locator strategies help testers, developers, and business technologists? What value can this feature bring?
Joyal:
Well, as we mentioned before, an advanced tester might find the most use out of this feature. In general, it makes their testing experience easier. But besides that, using a predicate string also makes it easier for less technical users of Qyrus to understand what is being searched for. Seeing “label matches ‘login’” makes it much easier to understand what the test is looking for than a long, exhaustive XPath.
Daniel:
And for developers, they’d find use in this, much similar to a tester. It would make their unit testing and quick tests much easier to create, run, and maintain in the long run.
Does the same or similar functionality exist without Qyrus, and how do competitors address similar problems?
Joyal:
There are a few competitors out there that do offer all these strategies already, but on Qyrus we are striving to make these strategies more usable for both experienced and newer testers.
Dan:
And when it comes to using these strategies outside of Qyrus, anyone can really do it when they’re scripting their own automated tests. It’s just that everything has to be done through code, whereas on the Qyrus platform, everything is no-code and simple to use.
Our features on Qyrus have the one goal of making testing more efficient, but that can be done in several ways. Speeding up the time it takes to build and execute tests, providing more insight into reporting, and enabling more intuitive test building are just some ways we are actively working to make testing more efficient.
How do you see these impacting day-to-day operations across organizations?
Dan:
Speed is really the main benefit of using these strategies. But there are some other advantages that can help to even further speed up day-to-day operations. “UIScrollable” can be used to automatically scroll the element if it is not in view, for example. This functionality is built into the locator strategy and is not possible with other strategies.
Joyal:
To further the topic of speed, the time taken to find elements during iOS testing is significantly reduced. For example, what might take an XPath strategy of 2.8 seconds to find an element can be done in 1.8 seconds with a predicate string and even quicker at 0.7 seconds using a class chain.
That wraps up this week’s Feature Friday. The drive for new and innovative testing strategies is greater than ever, and slowing down now could mean getting into a wreck in the future, so help protect yourself by switching to Qyrus as your testing platform! We hope that this weekend you take some time to slow down, stop, and enjoy some time off from your busy, racing weekly schedule. And then on Monday, maybe sign up for a Free Trial and check us out! Thanks again!
Notifications are everywhere in a person’s daily life nowadays. As per research done by the Pew Research Center, 97% of Americans own a cell phone of some kind, and 85% of Americans own a smartphone. This is astonishing considering that the last research done 10 years ago concluded that only 35% of Americans owned a smartphone. Not only that, but a third of high schoolers now own a smartphone.
With the evidence laid out in front of us like that, it’s a no-brainer that everyone everywhere is constantly getting notifications. And it’s about time that Qyrus joined in on that trend! Previously, we have talked about how we can give notifications via email to users to notify them about test executions, but now, we have a new feature that can enable Qyrus notifications in Teams and Slack channels! Joining us today are Milton and Kiwaun who’ll give us more insight into this topic.
Tell us more about the integrations with messaging apps offered by Qyrus and its use cases.
Kiwaun:
Yeah, so, basically what this feature enables users to do is set up Qyrus to deliver notifications to Microsoft Teams or Slack channels. This is a really simple feature, but one that can be considered super important for testers and developers.
Milton:
Email notifications are already a thing on Qyrus, but we all know how bloated our inboxes can get. Getting notifications for your Slack or Teams channels is much more convenient as a whole. That way, entire teams or multiple stakeholders can be notified instantly about test results. And lastly, if someone has those messaging apps on their mobile devices, they’ll also get these notifications on the fly.
Getting notifications on the fly is always helpful. Here at Qyrus, we seek to help. That is, it helps make testing more efficient, helps testers test smarter, and helps testers stay up-to-date with their testing landscape.
How might the integrations with messaging apps impact the testing process overall?
Kiwaun:
This feature only really has an impact on the reporting side of testing. The whole point is to get those notifications of test executions straight to your channel.
Milton:
But, overall, it can help in terms of effort reduction. Testers don’t have to manually log into Qyrus in order to view the report of an execution, but rather can just get that quick view of it as a notification in their Slack or Teams channels.
Like many features on Qyrus, this feature can be utilized by more than just testers. Qyrus helps to enable a better understanding of testing and the testing landscape that a company has by making everything more digestible when it comes to test building and even reporting and analytics.
How might this feature help testers, developers, and business technologists? What value can this feature bring?
Milton:
Obviously, testers would use this feature to get notifications straight to their messaging app channels, but developers can utilize this as well when they build and execute their unit tests on Qyrus.
Kiwaun:
Business technologists would get great snapshot information from these notifications, as well. They can stay up to date without having to get into the nitty-gritty of things or even navigate their way through the platform. They can get a great overview of what’s going on, all on the go.
Qyrus’ goal is to improve the day-to-day operations of everyone involved in the testing process. Our features are meant to make a lasting impression on how testing is done in an organization and impact how these action items are performed.
How do you see this feature impacting day-to-day operations across organizations?
Milton:
More than anything, this feature provides convenience so that the user does not have to log in and manually check tests every time they need to. That can be a waste of time, especially over a longer period of time.
Kiwaun:
On top of that, there are configurations that can be made that will help focus on what kind of notifications you will receive from Qyrus. This means that this is a tool for everyone.
Notifications surround us in almost every aspect of our everyday lives. Furthermore, notifications, in the future, will surely play an even larger role, as we can see a shift in cellphone and smartphone usage amongst Americans alone. Regarding Qyrus, we seek to further expand our abilities to notify users of their testing efforts and landscape. This is just one way in which we seek to further our capabilities. Thanks for joining us this week for Feature Friday. We hope you join us next week for more information on our myriad of features!
A Gartner study has mentioned that by 2024, 75% of large enterprises will use AI-enabled test automation tools for continuous testing. Also, 80% of the participants intend to increase the number of AI-based trials and proofs of concept, as per the World Quality Report survey. Such reports on industry trends indicate that AI-based automated testing is on the rise and on track for more than just a passing grade.
We at Qyrus believe that an AI-led quality assurance testing solution should be based on an approach guided by a continuous cycle of Discover >Understand > Predict > Respond.
Read this e-book to know:
How Artificial Intelligence help software developers and testers across industries?
How can Qyrus help in shaping the QA & testing space using AI?
How can AI make test automation more productive?
Businesses that deliver and maintain high-quality outcomes for customers over a sustained period are the ones that tend to rule the roost. And to that effect, enterprise CIOs—from technology startups to multinational companies are going all out to include high-performance, feature-rich, and secure software systems in their tech stack. But achieving this hyper-performance, hyper-quality vision is easier said than done.
Even organizations that have streamlined software and application development processes expect their development teams to improve the testing speed for faster time-to-market. In this conflicting environment, CIOs increasingly look for quality assurance processes for testing automation that helps them address end-user expectations more effectively and stay responsive to testing standards changes.
Download this whitepaper to know:
How CIOs can benefit from test automation
Key steps to ensure quality at speed in continuous testing
How Qyrus can help businesses in any segment to make their tests faster, smarter, and more quality-oriented
The year 2022 is now coming to a close and, with that, we come with our final installment of Feature Friday for 2022, as well. Over the last year, we have talked about numerous features and qualities of Qyrus that highlight just exactly how we improve testing. And, if you’ve been paying attention, you’ll realize that Qyrus is chock-full of useful tools and capabilities that improve all aspects of testing, ranging from the test-building phase to the test executions and, in the end, the reporting and analytics. And, along the way, we’ve made several small and large quality-of-life updates that aim to improve the smaller but still important aspects of day-to-day testing. So, today, we will take a stroll through memory lane and recap and highlight some features that augment different aspects of testing.
Features That Have Impacted Test Building
The aim of Qyrus is to enable testers to build tests in a more efficient manner. By reducing the amount of time it takes to build tests, the testing process as a whole has reduced its lifecycle significantly. There are many ways that we can help achieve this goal, but to highlight a few:
Mobile and Web Test Recorder
When it comes to building test scripts for mobile applications, Qyrus has a mobile recorder that enables users to build tests by recording user actions performed on a mobile device. It’s super simple and intuitive to use and is enabled by the click of a button. More advanced actions, like performing verifications, can also be recorded during this process. More information about our mobile recorder can be found here in this edition of Feature Friday.
And very much like our mobile recorder, Qyrus also has a web recorder. It does all the same great things that the mobile recorder does, allowing users to have test scripts built around recording their actions on a web page. The Feature Friday for web recorders can be found here and provides more information.
Inspect Mode
Qyrus also enables users to inspect elements on a mobile application. This means that more precise test building can be done. Instead of recording user actions, enabling the inspect mode gives users the ability to get locators of specific elements, as well as the ability to verify the existence of elements on a page. To learn more about inspect mode, you can find its Feature Friday here.
Reusing Test Scripts
Building, rebuilding, and rebuilding again is no way to go about creating your suite of test scripts. Qyrus enables users to reuse test scripts in multiple ways. This empowers testers to spend less time recreating some script that already exists out there. This can also help empower collaboration and teamwork. Click here to learn more about how reusing test scripts can help speed up testing.
Features That Have Impacted Test Execution
Once test building is out of the way, the continuous execution of test scripts is the next thing on the list. Comparing traditional Selenium testing to Qyrus is like comparing night and day when it comes to test executions. Qyrus already has all that one might need, and we’re here to highlight a few below:
Parallel Testing
Qyrus enables users to execute two tests at the exact same time. This already doubles our efficiency when it comes to test execution, but Qyrus can go even beyond that. Parallel testing in Qyrus gives users the ability to execute as many tests at the same time as their concurrency allows. This means that, if one has the resources, one can execute 5, 10, 20, or even 50 tests all at the same time. This means that Qyrus can scale to the needs of the client. Read more here about parallel testing.
Test Data Management
Test data management in Qyrus brings another testing tool into the fold. No longer do testers have to manage or create their own test data—or perhaps use a third-party tool for that—but instead it can all be done right on the Qyrus platform. Create test data manually, have Qyrus synthetically generate data for you, or grab data from an API call or database query. Click here to learn how test data management can augment testing today.
Parameterization
Utilize data-driven testing on Qyrus through the use of our parameterization feature. By selecting to parameterize specific steps in a script, a tester is able to take one script and have it cover multiple scenarios. As a simple example, imagine having a login script that can be parameterized to test not just one login, but the login of dozens or even hundreds of other accounts into the system. Through the use of test data management, parameterization becomes an even more versatile tool. Learn more about parameterization here.
Features That Have Impacted Reporting and Analytics
The most important thing, arguably, is how the reporting is generated by a testing system. Whether that be manually collecting screenshots of reports, keeping some spreadsheet to track testing progress, or using some other test management tool, reporting can oftentimes be fragmented and not adequate. On Qyrus, we automatically generate sharable reports that come with step-by-step analytics with screenshots and video evidence. However, that just scratches the surface as to what capabilities Qyrus has when it comes to reporting and analytics. Let’s take a look at a few features that augment this area:
Comparing API Reports
Although simple, this tool can be extremely useful in certain situations. Comparing API reports is a feature that Qyrus implemented to make life a bit easier for users who must constantly go back and forth between API reports. Although a small task, it can become rather tedious through repetition. This is a great example of how Qyrus takes into account user feedback and ways that we can help improve our platform to become even more all-encompassing when it comes to testing. Learn more here about comparing API reports and hear more from our team.
API Monitoring
Keeping up with the health of APIs, especially when there are a lot of them, can be quite a challenge. Ensuring that response times are in an acceptable range, that the API doesn’t go down every now and then, and that the responses are correct are all things that can take up a lot of time Qyrus has a useful tool that can do all of that for you and provide you with notifications about the health of your API. Read here about how API monitoring helps testers today.
Performance Profiling
Last but certainly not least is performance profiling. Qyrus is able to get performance profiling metrics for your mobile applications during test executions. This gives better insight for the tester into how an application might perform on different mobile devices or while performing different tasks. A slow or clunky application is not a good one, and Qyrus can help ensure the opposite of that for your applications. Click here to read more.
I hope that that stroll through memory lane helped jog your memory about a few of our testing capabilities and features. We’ve just scratched the surface here when it comes to that, however, and we still have so many more features to talk about in future editions! Qyrus is an ever-evolving platform that hopes to meet the needs of every tester across every type of testing. We’re like a one-stop shop when it comes to testing. Next year, we’ll touch on new features like Qyrus Bot, new updates to analytics and insights, as well as new updates to web, mobile, API testing, and so much more! New features are always just around the corner with Qyrus.
Thank you for joining us for our final edition of Feature Friday for 2022, and we hope you will join us for more next year! Happy holidays to everyone on behalf of the Qyrus team!
Topic: Unlocking Business Value with ROI Driven API Testing
Date: 15th December 2022
Time: 12:00 pm ET
Description: As per State of Quality Testing 2021, 61% of the organizations say APIs continue to be the leading type of testing they perform. In spite this significant chunk of API Testing, 43% of the developers say testing is their biggest pain point. So here we are, with another webinar, this time in collaboration with TechWell, a leader in software conferences covering Agile, DevOps, Test/QA, Requirements, and more.
Speaker Bio: Ameet Deshpande is an Engineering generalist and a builder at heart with a focus on Quality Engineering, Product Engineering, Product Management, cross-functional team building and Agile. He has been involved in many strategic initiatives at Qyrus and its clients and especially in Financial Services with primary experience in Quality Engineering, Cloud, SaaS, and AI. He was also involved in large scale transformation programs as part of a consulting & architecture groups within one of the top 10 Banks in the world.
Speaker Bio: Rahul Thakur leads enterprise sales at Qyrus and is a technologist at heart. Rahul has a background in consulting, technology, and private equity. He has been involved in several large scale strategic and technology transformation initiatives across multiple industries.
Did you know that 68% of developers expect to rely more on APIs this year, than they did last year? In an age when more organizations than ever depend on APIs to drive revenue, are seeking to capitalize on the API economy, and are adopting micro services, it’s critical to modernize API testing with automation.
Download Re-imagining API Testing: The Path to the Future.
Discover how to overcome the barriers associated with API testing and create dependable, high-performing, and secure APIs, quickly and cost-effectively. Get the speed, security, cost efficiency, quality, and test coverage your business needs to accelerate software delivery—and ramp up digital transformation and enhance customer experience.
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.
