The Latest

Automating test execution is supposed to give tremendous benefits, but often gives disappointing results—because it hasn’t met the objectives set for it. The fault may not lie with the automation itself, but with the objectives you are attempting to achieve. Aiming at the wrong target does not bring success! For example, objectives for automation are often confused with objectives for testing, but they should be different. In this article, learn how to avoid the most insidious traps and how to recognize good objectives for automation.

The mobile arena is in constant evolution, changing the way we approach software development both from a business and a technical perspective. Taking the time to set your plan can make the difference between success and just a good idea. In this article, Luis Carvalho shares some guidelines for bringing new applications into the mobile ecosystem.

A contract represents a service agreement between two parties, the bounded provision of service by one party to the other. This metaphor also applies to how we can think about the relationship between unit tests and code. A contractual mindset encourages test names and partitioning based on clear propositions, backed up with executable examples.

Release management is very similar to a team sport that involves many essential interactions. Very often teams find it particularly challenging to work together effectively, and the end result is that they cannot manage to complete any complex tasks without making many mistakes. Sports teams are also affected by interpersonal dynamics that can either help build the team or render it completely dysfunctional. Release management involves the packaging of every component in order to successfully deliver a complete product to a customer. Your release management function needs to efficiently coordinate the work of each player on your team.

This security testing strategy document describes the methods and tools used by security engineers to validate the security of a system. It also contains an outline of the approach the security engineering team will take to ensure that security acceptance criteria is met.

Implementing change can be a colossal challenge. People tend to prefer what's familiar, safe, and predictable to that which is new, unfamiliar, uncertain, confusing, or potentially risky. But the timing of a change effort can influence how readily people accept the change and adjust to it.

Suppose you have to start a new development team today: One of the items in the ‘to do' list would be to define the build and release management process for the product to be developed. In last 30 years Software configuration management has progressed from simple tools to fairly complex and feature rich tools. Some of the new-age continuous integration tools boast of simplifying and automating the entire build and release process. Still it is a Herculean task for the product development team to identify the right set of tools which would help in automating the entire build and deployment process. Most  project teams are not able to innovate beyond a limit and their build management system is mostly based on manual steps. Continue to read on if you have faced such a dilemma and are looking for an easy way out to this cognitively complex problem. The objective of this paper is to document the simple steps which would help a development team harness the power of automated build-test-deployment process.