Weighing in at under 150 pages, Testing in Scala by Daniel Hinojosa is a quick, project-based introduction to using a test-driven or behavior driven approach to testing in – you guessed it – the Scala programming language. Continued »
I had a great talk earlier this week with the CEO and founder of CloudBees, Sacha Labourey. It’s probably best to take this advice with a grain of salt, because Labourey does have a vested interest in the success of cloud services. CloudBees provides platform as a service (PaaS) for Java developers. Still, Labourey is a pretty straight shooter and I think he has a good deal of insight into enterprise application development. Continued »
The Software Quality Group of New England (SQGNE) is celebrating its twentieth season of getting Boston area software quality professionals together to talk about what’s important to the greater software quality community. Steven Rakitin, the group’s president, is pleased with the group’s progress – especially in light of the scant funding the organization receives.
Once each month (excepting August when the group breaks for summer vacation) SQGNE facilitates bright, motivated discussions about the issues that matter to testing and project management practitioners. On October 9, 2013, Harish Narayan led a group discussion on the changing roles of the quality assurance profession. Continued »
So JavaOne 2013 has come and gone. SearchSoftwareQuality.com staff have been busy at work pitching in with our sister sites to bring out some meaningful coverage of JavaOne and Oracle Open World. JavaOne is the event of the year for Java developers. Oracle Open World runs alongside JavaOne ever since Oracle bought Sun Microsystems and the JCP a few years ago. This year’s big Java news centered around a few big breaks for Java EE 7 and the new features coming soon with Java 8.
Last week the Boston Web Performance Meetup Group joined forces with Boston’s Mobile Experience Optimization Group to discuss issues around Web-based mobile app performance. The discussion was led by Ariel Weil, a representative from Yottaa’s adaptive Web performance team, and Ilya Grigorik just happened to be a part of the audience. The discussion centered more around user experience than I expected, but they definitely raised some good points. Continued »
I think it’s sort of human nature to be uncomfortable with the unknown and with the things that aren’t under our control. That might be one of the reasons so many software quality professionals try to skate around doing security testing. Obviously there are other factors – getting caught up in pressing functionality or usability issues for one – but I think security is secretly scary for some of us. That fear is probably tied mostly to the number of aspects of application security that are out of our own reach.
A week ago today, I sat in on a really interesting informational workshop. I learned all the basic pieces of building an incredibly simple mobile application. I write a good deal about mobile application development, but as yet, I hadn’t actually done any coding for a mobile app. I still don’t think I’ll stop writing about it and start doing it any time soon, but I do now have a much better appreciation and understanding of the practice of building mobile applications. The demonstration application we built was a simple HTML 5 app designed to run on multiple platforms – iOS, Android, and Windows Phone, for the most part. Continued »
This week it’s a quick wrap-up of recent content on SearchSoftwareQuality.com before I head out for the weekend. Jenn Lent shows us the places where automation falls short of the hype. Jan Stafford shows us a couple of Agile success stories. But first, let’s look at some of the things application security expert Dan Cornell has been up to. Continued »
This week I’m going to bring up a few things I got to see at Agile 2013 in Nashville last week that I should have written up while I was at the conference. These are the extra blog posts I planned last week but didn’t have time for, all rolled into one. I’ll write about Legos, asking questions, and bluegrass music. They all relate to Agile in one way or another.
Automated integration testing sort of presents us with a paradox. The problem is that automated testing makes the most sense for large organizations where there’s a lot of testing to be done; however, these big enterprises tend to have large, complicated development environments where it tends to be hard to build automated tests for integration. So, it’s not quite a catch 22, but it is rather inconvenient that the more an organization needs their integration testing automated, the harder it’s going to be automate it. A growing open source project might have found the trick to cutting the knot – if its name doesn’t get in the way too much. Continued »