Test architecture means the way you put together all those things you need in testing. Depending on what you test, where, and how, the test architecture may be simple or complex, ad-hoc or well-thought. Most often than not, test architectures are not thought of, they just emerge.
International experts for software quality cooperate in the GFFT Software Lab. Qentinel, a leading specialist in test automation, and the GFFT (Society for the Promotion of Research Transfer) are launching a consortium project on "Software Testing in the Automotive Cloud" in 2021. The aim is to develop practice-oriented solutions for the special challenges of connected driving. Interested software testers, software developers and automotive engineers are cordially invited to exchange personal experiences. Several (online) workshops are planned for 2021, focusing around Android Automotive, Adaptive Autosar and Test Automation in the Cloud.
"If someone asks me what cloud computing is, I'll simply tell them that it's a better way to run your business." Salesforce founder Marc Benioff.
The Challenge: Automating C++
We started a collaboration with TietoEVRY regarding test automation for AUTOSAR. They had implemented a PoC of Execution Management which is a functional cluster in Adaptive AUTOSAR Platform. Execution Management handles startup, monitoring and shutdown of Adaptive Applications, but the system built on C++ was missing a comprehensive and scalable testing solution.In Adaptive AUTOSAR services and APIs are implemented using C++. Qentinel Pace, a cloud based hyper-scalable test automation platform, is known for its ability to automate UI-level testing of web-based systems. Could Qentinel Pace be used to automate testing for Execution Manager functionality?
Qentinel Pace is Qentinel’s cloud-based test automation platform. It was built on three premises: scale, speed, and transparency. Because the scale of testing keeps growing test automation platforms must scale, too: from a single developer to a large organization, from small test volumes to huge volumes – and back. Because the software release times are shrinking, testing must be fast: time must not be wasted on patching test environments or maintaining cumbersome test cases. Because both speed and quality are important, decisions about releasing software or changing something in the software process must be fast and fact-based.