{"id":444,"date":"2003-07-03T16:53:15","date_gmt":"2003-07-03T20:53:15","guid":{"rendered":"http:\/\/wordpress.cephas.net\/?p=444"},"modified":"2003-07-03T16:53:15","modified_gmt":"2003-07-03T20:53:15","slug":"jakarta-latka","status":"publish","type":"post","link":"https:\/\/cephas.net\/blog\/2003\/07\/03\/jakarta-latka\/","title":{"rendered":"Jakarta Latka"},"content":{"rendered":"

I have a peculiar interest in testing tools… I’ve mentioned JMeter (which is more of a stress testing tool) a couple times before, I just found a new one on the Jakarta site call Latka<\/a>, which “… is a functional (end-to-end) testing tool. It is implemented in Java, and uses an XML syntax to define a series of HTTP (or HTTPS) requests and a set of validations used to verify that the request was processed correctly.<\/i>” <\/p>\n

The cool thing about Latka is the non Java part… anyone that understands a little XML can create and\/or edit an xml document that defines an ‘test’ and then run it using the Latka engine. So for instance, here at Mindseye<\/a> our QA team is composed of invididuals with a small amount of programming experience. They could easily create a Lakta test using the xml syntax and then automate the testing of various applications using Latka. Still not convinced, here’s a sample test:<\/p>\n

<?xml version=”1.0″ standalone=”no”?>
\n<!DOCTYPE suite PUBLIC “-\/\/Apache Software Foundation\/DTD Latka Test Suite 1.0\/EN”
\n   “http:\/\/jakarta.apache.org\/commons\/latka\/dtds\/1.0\/suite.dtd”>
\n<suite defaultHost=”http:\/\/www.mindseye.com” label=”mindseye”>
\n   <request path=”\/whymindseye\/default.cfm” label=”why you should choose mindseye” method=”get” secure=”false” followRedirects=”true”>
\n      <validate>
\n      <statusCode code=”200″ \/>
\n      <regexp pattern=”What drives landmark companies” \/>
\n      <\/validate>
\n   <\/request>
\n<\/suite><\/p>\n

Save this to a file and then type:<\/p>\n

latka file:PATH_TO_FILE<\/p>\n

from the command line. It should check that the page http:\/\/www.mindseye.com\/whymindseye\/default.cfm returns an HTTP status code 200 and that it contains the phrase “What drives landmark companies”.<\/p>\n

Unfortunately, Latka doesn’t appear<\/a> that anyone is working on it (at least since last July). <\/p>\n

On a related note, I also found this Slashdot discussion on “Testing Products for Web Applications?<\/a>“.<\/p>\n","protected":false},"excerpt":{"rendered":"

I have a peculiar interest in testing tools… I’ve mentioned JMeter (which is more of a stress testing tool) a couple times before, I just found a new one on the Jakarta site call Latka, which “… is a functional (end-to-end) testing tool. It is implemented in Java, and uses an XML syntax to define … Continue reading Jakarta Latka<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,2,12,10],"tags":[],"_links":{"self":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts\/444"}],"collection":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/comments?post=444"}],"version-history":[{"count":0,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts\/444\/revisions"}],"wp:attachment":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/media?parent=444"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/categories?post=444"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/tags?post=444"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}