The IT Side: January 2012

Wednesday, January 25, 2012

Lately I've been involved in a lot of software testing and came across this awesome article about it:

Top Five (Wrong) Reasons You Don't Have Testers

I find this guys blog very insightful and like the list of checks he recommends for software development:

Do you use source control?
Can you make a build in one step?
Do you make daily builds?
Do you have a bug database?
Do you fix bugs before writing new code?
Do you have an up-to-date schedule?
Do you have a spec?
Do programmers have quiet working conditions?
Do you use the best tools money can buy?
Do you have testers?
Do new candidates write code during their interview?
Do you do hallway usability testing?

Tuesday, January 24, 2012

My WSDL Cheat Sheet

Service -> ‘Java Class’

Operation -> ‘Java Function’ The Operation defines the name of the Operation and ties the request response messages together.

Port -> A service is assessable on a Port. A Port has a unique name space and binding attribute. The Port specifies the service address. Web service can be exposed as SOAP or HTTP. The same web service can also be exposed by multiple Ports.

SOAP example:

<port name='WeatherSoapPort' binding='wsdlns:WeatherSoapBinding' >

<soap:address location='http://localhost/demos/wsdl/devxpert/weatherservice.asp' />

</port>

HTTP example:

<port name='WeatherSoapPort' binding='wsdlns:WeatherSoapBinding' >

<http:address location="http://localhost/demos/wsdl/devxpert/weatherGET.asp"/

</port>

Message -> Normally two messages required i.e. input message and output message. Messages contain zero or more <part> elements. Sample messages below

<message name='Weather.GetTemperature'>

<part name='zipcode' type='xsd:string'/>

<part name='celsius' type='xsd:boolean'/>

</message>

<message name='Weather.GetTemperatureResponse'>

<part name='Result' type='xsd:float'/>

</message>rt name='WeatherSoapPort'

Binding -> ‘Ties it all together’ - specifies binding(s) of each operation in the PortTypes section