Last month, we wrote here about a cool (and FREE!) downloadable ebook from CA, titled Dysfunction Junction: A Pragmatic Guide to Getting Started with DevOps. Riffing on the same theme, CA has published a cool (and FREE!) slideshare that distills the myths related to DevOps.
If your organization isn't using Service Virtualization yet to develop software better, faster and less expensively, you're missing out. We're not saying you might be a redneck, but ... here are 17 signs you really should look into SV.
It was nearly two years ago that the Theresa Lanowitz and her colleagues at voke published some of the first solid research on Service Virtualization.
To recap, that empirical study found converts to Service Virtualization reporting a dramatic decline in development constraints – and a corresponding decline in cycle time. On average, respondents said their software cycles were down 23 percent.
Well, Lanowitz & Co. are at it again. Their latest study, which runs until Oct. 13, seeks a deeper understanding of the SDLC in enterprise IT organizations and how much Service Virtualization is helping to deliver products to market faster and less…Continue
Hi,I have recorded JDBC traffic successfully and deployed, but i am not able to invoke, please guide me how to invoke the service.once deployed i got the url in the service console lisasim://localhost:299[?/?]I appreciate your help regarding the same.Continue
I executed a test suite on server (by right-clicking on the suite in my workstation). After that, I went to LISA Server Console and reporting tab. I set the time frame filter within which I executed the test suite. But I’m not seeing the results. What am I missing?FYI: My registry, simulator and coordinator services are up and running perfectly on my LISA Server machine.Continue
Hi all,I have LISA Wks on one Windows machine and LISA Svr on another machine (Windows Server). On the Server, I have Registry, Coordinator and Simulator running as services.I have created projects on my Wks machine and stored them locally. Now when I'm trying to run the test case using commandline utility as follows, I'm getting errors:TestRunner --testCase C:\full\path\to\testcase.tst --stagingDoc C:\full\path\to\StagingDoc.stg -config C:\full\path\to\Config\project.config -cs…Continue