Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It only takes a minute to sign up.
Sign up to join this community
I am searching for an open source tool to record the functionalities of a desktop application functionalities like starting and ending time of each operation like load report rendering and maintain the log of every single action as well.
Any recommendation for desktop applications?
If you want to test application itself - the profiling tool for the programming language the application is written in is the best choice.
Alternatively you can use "normal" desktop automation tool like Appium or LDTP
In case you want to simulate hundreds/thousands of applications concurrently accessing backend/database - you need to find a tool which supports network protocol(s) used for this communication, see How to Do Desktop Performance Testing article for more information
While working in a software testing company, I have experienced such requirements i.e. doing performance testing using an open-source tool. Apache JMeter is one of the best tools available in the market and high-level details are mentioned below -
"JMeter comes with the HTTP(S) Proxy Server, which can capture the requests between the web browser or mobile device and the backend and convert them into HTTP Request samplers."
So, if the desktop application you need to test uses HTTP or HTTPS protocols for communicating with the backend server, you should be able to record the requests with JMeter and replay them with an increased number of virtual users
Therefore you can use JMeter for load testing of almost any desktop application which communicates with the backend over HTTP.
I have a non-answer that maybe should be a comment, but nevertheless-
Have a built in logging and monitoring system measuring those actions, preferably one with a level that you can control so i is not too "noisy" when used in production. This will allow you to test what you need but also test in production and identify problems before they become a real problem. If you properly build the infrastructure then it becomes a no-brainer for the developers to sprinkle those measurements wherever needed.
