What is the GLU V-Model of Testing?

Since GLU.Ware is a no code system, there is no need for developers. Thus the ‘traditional’ V-Model of testing is ‘truncated’ as it is the Analyst who will configure and build the integration Engines. This means that there is no need to wait for a typical 2-week sprint cycle before the Analyst can test the integration. Rather, with the GLU V-Model, Analysts can iterate through the Configure, Build, Deploy, Test cycle within minutes. This is what enables GLU.Ware users to Innovate at Speed. 


Fill the form and we’ll contact you shortly

    I agree with

    We uses cookies to make your experience on this website better. Learn more
    Accept cookies