How Apica provides insights into performance

apica, which began in 2005 as a load testing company, transitioned beginning in 2010 into monitoring That’s because they noticed organizations doing load testing were breaking it off into separate teams, which tend to use different scripting methodologies and pre-existing tools but it’s the convergence of these different tool sets that is becoming very powerful, according to ben Jolley, vice president of marketing for apica

“We’ve actually been able to solve critical problems much, much quicker,” he said “We created what we call these desktop application checks, which gives us the ability to do rPa functions on anything because the [apica] agent can basically do anything that you can do with a Windows or Linux system, you can do this for any application in any protocol so we specifically focused on browser checks, which is 85% of the internet traffic but we can also do things like monitor web streams, and monitor them end to end for things like color code, color palette, how those pieces actually work We can do another depth and go further into application flows. so we can basically do any protocol out there that exists on the internet by opening up and writing

“The idea,” he continued, “is that you’re going to get consistent testing bases across all these different scenario types and that consistency is the big piece, because what you wind up having is some groups that do some testing with one tool, other groups that do testing with a different tool and then things could slip through the cracks because they don’t cover each other’s gaps ”

Jolley pointed out that apica is not a full application usability testing platform. “you give us the scenarios and then we load them up and then we can do them repeatedly in a Ci/Cd pipeline or at scale because we will basically take anyone’s scripts, convert them and make them work and it’s this level of enablement that we provide that allows us, a small company, to be in some really big banks and big ioT shops these days.” n