Always have the most current updates on software, Agile, mobile development, testing and more right at your fingertips.
Current Articles | RSS Feed
Last week I delivered a Webinar entitled, “How to Implement Code Reviews that Don’t Suck.” I focused my presentation on how to overcome common challenges to getting a successful code review process in place. This is an important topic, because as clear as the benefits are, there are often social, organizational, and education barriers to getting started, being productive, and achieving and measuring success.
Read More
Yes, SmartBear was scoping out the STAREAST Conference in Orlando last week. It was a well-organized and well attended event. As an attendee put it – “I had budget to attend one conference this year and I chose this one because of the community. It is the community of testers that makes events like this exciting and worth attending.”
Earlier this week Luxury Daily reported on AlertSite’s analysis of the Web page load speeds and site availability of the top luxury brands in retail and automotives in Q1 of 2012. It’s clear that, unlike several other industry sectors, luxury brands take the quality of their website performance just as seriously as the quality of their products and services.
The latest version of soapUI, soapUI 4.5, brings us a new approach to validation. The key improvements are:
Sin City, here we come again! This week, Monday through Wednesday, our AlertSite team is attending the Imagine eCommerce Conference in Las Vegas.
This is the fourth installment of blogs regarding the Top 5 Agile Testing Challenges.You can view the prior blogs or download a more detailed white paper, here:
Thank you so much for your participation in the webinar Continuous Load Testing in Agile Environments by Michael Punsky. The webinar was well attended and we also had an excellent discussion with many insightful questions. The On-Demand recording of the presentation and the Q&A session can be found at the link above.
It’s not that the other developer purposely created a hard-to-maintain application. It’s that you don’t know the other developer’s thought process in putting the application together, making it difficult for you to figure the code out without some help. This article provides some tips to ease the pain and get you started more quickly.
This is the fourth installment of blogs regarding the Top 5 Common Problems for Agile Testing Teams. You can view the prior blogs or download a more detailed white paper, here:
I wanted to take a moment to introduce myself as I've just begun blogging here at SmartBear. I am excited about the opportunity to discuss with you and help solve challenges related to the world of software quality, testing, and also share opportunities for technical and business innovation. You may follow and connect with me on Twitter or on Linkedin.
This is the third installment of blogs regarding Agile Testing Challenges. You can view the prior blogs or download a more detailed white paper, here:
No matter the industry, every business deals with the task of allocating resources to the items that have the highest return on investment. Unfortunately, identifying all of the items that have the biggest impact on the bottom line can be a complex task. There is one item, however, that stands out as having a broad impact on many critical elements of every software business: software quality. For successful businesses that develop software, software quality cannot be an exception--it must be the requirement. While customers will obviously prefer quality software products, that’s only the tip of the iceberg.
One of the touted advantages of cloud computing (especially Software as a Service) is that it removes the need to support older application versions. The IT department doesn't have to worry about keeping end-user software in compliance with security patches or upgrading the business’ computers with commercial applications (such as Microsoft Office) or custom in-house software. Developers appreciate this, too, since with SaaS, nobody issues trouble tickets on the 3-year-old version of the application which users refuse to relinquish.