Productivity

It is a difficult decision to know when it is best to deliver a reporting solution over a control implemented solution. In part 2 of this series we dive deeper into a case where a reporting solution should be used.

Greetings, fellow testers. Last week we talked about Data Driven Tests and how they can speed through dozens or hundreds of variations quickly for you. In the example I used a simple sample application, just a web page with a form. Often we need to log in and/or perform some setup steps before the actual "meat" of the test, or have some cleanup tasks after we're done — we certainly wouldn't want to do that for every iteration. That would be silly and time-wasting. Let's look at a better way. Here's our simple test, modified to use a login screen. ...

INotifyPropertyChanged and INotifyPropertyChanging interface implementations for all persistent properties will be only one click away with Q2 2013 of OpenAccess ORM!

It's a tough decision to know when it is best to use a reporting solution or when it's better to use a control suite. In part 1 of the series, we go over some of the high-level criteria that can help you along in your decision then dive into a control suite sample using live data and the RadChartView control for WinForms.

Greetings, fellow testers. A couple of weeks ago, I wrote about Manual Testing using Test Studio. As I pointed out, brining your existing manual tests into Test Studio is a great way to get started, and provides a better platform for reporting results over time than simple spreadsheets normally do. Your next step might be to take advantage of Test Studio's automation to ease your way through actually performing the manual tests. You probably have many tests that begin with the same set of instructions - log on, navigate to a particular page, perhaps creating some data - before ...