Verification and Validation: The Difference
by Jeffrey Martin
I've been asked several times recently about the difference between
Verification and Validation in automated testing and for some advice on
applying and documenting each kind of testing. Let me first take a minute to
define these terms.
Verification Vs. Validation
Verification is testing that your product meets the specifications /
requirements you have written. "Did I build what I said I would?"
Validation tests how well you addressed the business needs that caused you to
write those requirements. It is also sometimes called acceptance or business
testing. "Did I build what I need?"
V&V; together make sure that your software has delivered on its purpose in an
error-free (ideally) way.
Using V&V; in Your Workflow
In a more traditional Waterfall process, with Specifications and Requirements
defined at the sta... (more)
Who Is Responsible for "Good Code"?
by Erik Dietrich
A few weeks back, I wrote a post about getting ready to address a coworker's
bad code. This sparked some conversation across various media, including
the following interesting question:
...seems that there is a breakdown in managing the development process. Why
is Bob allowed [to keep] writing bad code?
Measuring Developers
This feedback is interesting enough to merit a blog post in and of itself. I
recognize a question that cuts to the heart of a software development
conundrum when I see it. The structure of most organization... (more)
How Beacons and the iBeacon Protocol Fit With the API and the Internet of
Things
By Jennifer Riggins
Forbes called 2015, the Year of the Mobile Beacon. AdWeek talks about how
beacons are already influencing the way we network, get
drunk, vacation, shop, and even how we buy sausage. Ten experts
at Marketing Land predicted that this year the whole world of mobile
marketing will become acutely location-aware. Plus, if Google, Apple, and
Facebook are betting on it, shouldn't you? We'll dive in and learn how
beacons interact with APIs, how the different beacon protocols work, and w... (more)
Nine Reasons Microservices Matter to Architects, Developers & Testers
by Les Worley
Several years ago, I was a developer in a travel reservation aggregator. Our
mission was to pull flight and hotel data from a bunch of cryptic reservation
platforms, and provide it to other companies via an API library - for a fee.
That was before companies like Expedia standardized such things.
We started with simple methods like getFlightLeg() or addPassengerName(),
each performing a small, well-understood function. But our customers wanted
bigger, more encompassing services that would "do it all.... (more)
IoT Is Busy Innovating, But Where's the Integration? Thoughts from O'Reilly
Solid
By Paul Bruce
Last month, SmartBear was out in full form at O'Reilly Solid, a conference
all about the Internet of Things (IoT) [this year]. We chatted with anyone
and everyone who is building APIs to support their cool gadgets or back-end
systems. What we found was...curious.
What Is the Internet of Things to Everyone Else?
The concept behind the Internet of Things has been around for a while now,
ATMs being some of the first enterprise, hardened, network-connected, managed
devices for mainstream c... (more)