profile image
Marianne Hollier
Client Advocacy Manager for Test Automation and Service Virtualization
About
Marianne Hollier is an Open Group Master Certified IT specialist in application development. She has strong practical expertise in measurably improving the software development lifecycle and driving the necessary cultural changes to make it work. Marianne is instrumental in architecting, tailoring, and deploying best practices and appropriate software development tools on many types of projects—from large to small, long to fast-track, agile to traditional. Marianne is passionate about all things testing—process, tools, culture, and automation. Her experience is broad-based, spanning both custom projects and standard software packages that apply to pharmaceutical, refining, telecommunications, healthcare, financial, automotive, government, and retail industries.
Posts by Marianne Hollier
article-img
Automation Secure DevOps | January 24, 2020
Dispelling Continuous Testing Myths
You may have seen the term “continuous testing” and thought it was just the DevOps flavor of the month. Some might even think it isn’t part of DevOps or isn’t for cloud or hybrid cloud applications. Well, think again. As it turns out, there are a few more fallacies around the idea of continuous testing floating around the application development community. Here are a few to ponder: Continuous testing is only about executing test scripts Limiting the term “testing” to only the execution of test scripts is a misnomer. As my co-author, Allan Wagner and I point out, testing and checking application functionality are not equal. There’s a long list of testing items to check off one’s list, the least of which is collaborating. Continuous testing is merely a buzzword  Guess what? It’s a core part of that essential DevOps practice, continuous delivery. And, with customers demanding higher quality software faster, it isn’t going anywhere soon. In short, invest in continuous testing. Only agile teams do continuous testing This is false. Some or all parts of continuous testing are critical for any type of team as well as all players. This includes test automation, production-like test environments and realistic test data. A related myth—only testers contribute to testing—is also not true at all. The idea of continuous testing includes all team members. The book describes the roles everybody has to play. For example, did you know that designers can improve testing? They can work with testers to help them understand where the fragile parts of the application are. Automating tests means we need fewer tests No, the machines are not taking over. Automating tests does not mean cutting back on testing jobs. To the contrary, automation is reducing testers’ needs to act like cyborgs and spend more time doing what...
article-img
Automation Secure DevOps | September 11, 2019
Customer-centric approach key for advocacy program success
The HCL business philosophy is based on a customer-centric approach. Thanks to our Client Advocacy Program, customers can have a direct point of contact for the test automation and service virtualization suite of products, enabling them to create a strategic relationship with our technical, management, and executive leaders. The products included are: HCL OneTest Studio HCL OneTest UI HCL OneTest Performance HCL OneTest API HCL OneTest Virtualization HCL OneTest Embedded HCL OneTest Data The HCL Client Advocacy Program is based on five fundamental points: A cohesive and collaborative approach to the client relationship Proactive communication on product news and updates Support for in-depth product understanding and business needs Deep dive into customer business and challenges Frequent interaction during the product roadmap definition and the development process What do advocates expect from customers participating in the Advocacy Program, and what is asked? The client’s role is to share with the Client Advocate (CA) their business needs and strategies, communicate to the CA their expectations and product experience, and share their issues and requirements. The customer might involve the CA in planning meetings to take advantage of suggestions while defining the right direction according to the business needs. CAs do not replace the official channel of support but they can be a fast path inside the development lab organization. Building a long term strategic relationship with the advocates The CA’s role is to facilitate the flow of information between clients and the HCL technical community. By having regular interactions with the client, CAs become aware of the customer environment. They learn of any issues or requirements, as well as understand customer business goals and strategies. CAs are involved in planning sessions, upgrade plans to provide assistance, or help the customer support, services, and development teams to understand the customer needs clearly. CAs...
a/icon/common/search Created with Sketch.