Skip to content

Feed aggregator

The Art of DevOps Part III – Staging Grounds

In this 4 part blog series, I am exposing DevOps best practices using a metaphor inspired by the famous 6th century Chinese manuscript: “The Art of War”. It is worth reminding that Sun Tzu, just like me, considered war as a necessary evil, which must be avoided whenever possible. What are we fighting for here? […]

The post The Art of DevOps Part III – Staging Grounds appeared first on Dynatrace APM Blog.

Categories: Companies

Real World Experiences: Blackboard

Sonatype Blog - Tue, 04/21/2015 - 22:13
As part of a new series we're calling 'Real World Experiences' we'll be highlighting how Sonatype customers are benefiting from greater development efficiency, higher productivity levels, faster time to market and better quality software, all while being more secure. We kick off the series covering...

To read more, visit our blog at
Categories: Companies

Tricentis and Automic Partner on DevOps

Software Testing Magazine - Tue, 04/21/2015 - 19:21
Tricentis and Automic have announced a strategic partnership to enhance Automic’s release automation product with Tricentis’ testing capabilities. The combined integrated solution will enable enterprise customers to automate the whole release process, including testing. Together, Tricentis and Automic will accelerate the application journey from development to production, while communicating with teams and systems needed at each step. Greater automation, increased risk coverage and a lower number of test cases dramatically reduces testing time, effort and costs; all critical requirements for a fast-paced, innovative DevOps team. As a result, Tricentis is the ...
Categories: Communities

QASymphony Updates Testing Tools

Software Testing Magazine - Tue, 04/21/2015 - 19:05
QASymphony has announced updates to its product suite today that accelerates its leadership position in the agile testing and data visualization market. The release includes updates to the company’s popular test case management tool, qTest, and exploratory testing tool, eXplorer. “As an agile company, we are constantly iterating and looking for ways to improve our product,” explained Kyle Cochran, VP of Product at QASymphony. “This release is a prime example of our dedication to both constant innovation and delivering on our customer’s needs.” This release includes improved test automation, enhanced reporting ...
Categories: Communities

Rapise 3.0 Released - Provides Mobile Device and Exploratory Testing

SQA Zone - Tue, 04/21/2015 - 17:41
Inflectra has announced the release of Rapise 3.0, the most comprehensive and powerful automated testing suite on the market. The latest version includes support for the testing of mobile devices (including native apps) on iOS and Android devices ...
Categories: Communities

Rapise 3.0 Supports Mobile and Exploratory Testing

Software Testing Magazine - Tue, 04/21/2015 - 17:37
Inflectra has announced the release of Rapise 3.0, the most comprehensive and powerful automated testing suite on the market. The latest version includes support for the testing of mobile devices (including native apps) on iOS and Android devices and support for exploratory and manual testing. New Features * Ability to record exploratory manual tests and import into SpiraTest / SpiraTeam * Playback of manual tests and hybrid manual-automated tests * Support for testing on Android mobile devices * Support for testing on Apple iOS mobile devices * Ability to create, edit and manage manual tests and ...
Categories: Communities

Software Testing Industry to be Valued at $71 Billion by 2018

uTest - Tue, 04/21/2015 - 17:10

Mobile-AppsApple is releasing its polarizing-yet-hotly-anticipated Apple Watch this week amongst much fanfare, and just capped off a couple of quarters with its most successful iPhone sales ever. The just-released Galaxy S6 was labeled the best Android phone of all time, and will likely sell like hotcakes, along with its S6 Edge counterpart.

On the apps side, where these devices truly shine, you’ve got Snapchat valued at $15 billion. And this is a business model that has only started to generate any revenue.

Is it any wonder, then, that by 2018, the global software testing industry will be valued at nearly $71 billion?

The estimates are from a statement by the Malaysian Software Testing Board, and a recent independent report by Technavio, a technology research and advisory company under the Infiniti Research group, based out of the UK. And this estimate is nearly doubled from the US$41.84 billion valuation of the industry in 2013.

The wearables market with the Apple Watch, and yet-to-be-finalized Internet of Things technologies undoubtedly factor into the projected explosion in growth of the market. Organizations are especially weary of these new technologies as they’re totally new ecosystems of apps — the need to test on multiple devices and envrionments will be more urgent than ever with too many lingering question marks for organizations.

It’s a good time to be an app developer…and a tester.

Not a uTester yet? Sign up today to comment on all of our blogs, and gain access to free training, the latest software testing news, opportunities to work on paid testing projects, and networking with over 175,000 testing pros. Join now.

The post Software Testing Industry to be Valued at $71 Billion by 2018 appeared first on Software Testing Blog.

Categories: Companies

Should You Test in Production ?

Software Testing Magazine - Tue, 04/21/2015 - 16:38
Although it could appear like a counterintuitive concept, the idea of performing software testing in production has gained more and more visibility in a software development world that aims for rapid delivery of new features and where it could be more and more difficult to reproduce the full complexity of applications in a separate environment. In this article, Marc van ’t Veer discusses the concept of testing in production and why it should be performed. Testing in production can be defined as testing on a real live system, either about to ...
Categories: Communities

5 Proven Strategies to Get More App Reviews

Testlio - Community of testers - Tue, 04/21/2015 - 16:14

App reviews don’t happen by themselves.

Users tend to download the first app that appears on their search result. App reviews is one of the factors that decide which gets to be “that app” among other lookalikes.

It’s hard to figure out how to ask for an app review effectively. Check out these five strategies that worked for me:


1. Be sincere

Personality matters.

People always appreciate sincerity.

App review pop-ups can be annoying at times. However, they are beneficial to both the service provider and the customers. Lots of people like the idea of Snapchat, but what if there’s a bug wiggling around that prevents them from using it? If users can tell Snapchat what’s wrong, Snapchat can then fix the issues and make their users happy. The app gets better, the users get all the benefits. It’s a win-win. If your users can see the impact of their opinions, they’ll gladly help.

Pay attention to the content, your app rate request isn’t just a pop-up. Kindly ask for a review and don’t forget to thank your users. Make them feel they are contributing. It’s an opportunity for you to get closer to them. They’ll see that you care. It will help set you apart from your competitors.

Your pop ups presentation can look as basic as possible. It’s better to be basic. There are only three options that your users will care about: Yes, No or Later.

These guys do pretty well:


“Showing us some love on the store helps us continue working on the app and make things even better!”

“Sorry to hear you didn’t want to rate our app, tell us about your experience or suggest how we can make it better then?”

This feels like a more personal conversation than bluntly asking “hey, rate our app”. A sense of contribution is heightened among users. It’ll increase your chance of getting app reviews significantly. A little effort goes a long way.


2. Look Further Than App Store Rating

App store reviews aren’t the only way to get positive feedback from customers and boost your app ranking.

Satisfactory in-app FAQs and support is another way to collect feedbacks without having to depend on app store reviews. It can even encourage users to rate your app. If I walk into a restaurant and the server was nice to me while patiently answering every question I have about the menu, I would tend to leave a bigger tip and even write a note on my bill saying, “Thank you! I had a great night!”. It works the same way for app reviews.

One suggestion is to try out Helpshift. It’s been used by a number of accredited startups and companies. The product lets you invite your team to help with its in-app services. These services include in-app FAQs and support. Users can message your team directly for help, which can increase engagement and boost customer satisfaction.


Helpshift will identify loyal customers first then ask for the app rate later. This way, your users won’t feel pushed to rate your app.The timing needs to make complete sense.

ModCloth does a great job of engaging customers to give feedbacks voluntarily. It asks users to rate their dresses in detail after delivery. I can clearly see they are trying to improve their design by asking for my measurements, comfort level, fabric quality, and how happy I am with the item purchased. They made a girl feel special and cared for. I was more than happy to leave them feedback.



3. Don’t Be So Forward

We are usually told by our friends the world would be so much easier if everybody was straightforward about what they want. Though it might be true in most cases, asking someone to rate your app is a different story.

We all hate being slapped by the coldhearted “Rate Our App”-”Yes/ No/ Remind me Later”.

How about playing the “the game” first?

“Hey are you free at 12? Do you want to go get lunch with me?”

“Sure I’d love to.”

“Oh hey since we’re getting lunch, we should also be dating.”


That’s probably not the way you should ask somebody out, but that’s the way you should try to ask for an app review.

Here’s a good example from Circa News:

circa news

It’s simple. It’s friendly. It’s flexible.

Here’s the nut of Circa New’s strategy: It helped the app to avoid negative ratings. If somebody denied your invitation to lunch, maybe it’s not a good time to ask them out on a date anyway.

The app observes a user’s experience first. Then, it takes users to two different options. If they said they did not enjoy the app, it will direct them to where users can give in-app feedback. Therefore, Circa News avoided negative ratings. Developers will still be able to receive reviews from users and improve their services. On the other hand, if users said they enjoyed the app, they will be requested to rate it. Users will either give positive feedback on the App Store or simply, no feedback at all. Negative feedback is deterred. Genius!


4. Incentivize Users


I don’t know how much I love Jelly Jumble, but I sure love those 100 coins!

Giving users rewards for rating your app makes everybody happy. Freebies are the best.

However, try your best to avoid asking users to rate you 5 stars. It’s not illegal, but it’s better not to. You want honest feedback to improve your services, not bubbles. 1 or 5 star ratings tell you nothing. It’s the 3s and 4s that you should pay attention to.


Update: I was just informed that developers are no longer able to offer incentives to get users to rate their apps. 


5. Build a Good App

This is the most important part. 

If your app is not good enough, people won’t use it. Without a user base, there’s nobody there to rate your app.

Make a really good app and deliver the best services. Make your users happy. People will rave themselves, because they know you deserve it.

Check out how Slack wins its users.


What do you think about these strategies? What do you think are the most effective ways to get more app reviews? Did you successfully approach your users? We’d love to hear your opinions below.

The post 5 Proven Strategies to Get More App Reviews appeared first on Testlio.

Categories: Companies

Test Management Summit, London, UK April 28-29 2015

Software Testing Magazine - Tue, 04/21/2015 - 09:50
The Test Management Summit is a two-day conference focused on software testing that takes place in London. The first day will consist of workshop and the second day of discussions. In the agenda of the Test Management Summit you can find topics like “Techniques for Successful Program Test Management”, “Security – What can testers do now?”, “Putting Models at the Heart of Testing”, “Testing the Internet of Things: the Dark and the Light!”, “Rapid and Effective Team Building Techniques”, “Improving the effectiveness of reviews and Inspections”, “Software versus Project Test Management ...
Categories: Communities

May and June Workshop Reminder

Ranorex - Tue, 04/21/2015 - 09:11
This is just a quick note to remind you about our upcoming Ranorex training courses scheduled for May and June.

Get firsthand training with Ranorex professionals and learn how to get the most out of Ranorex Studio and the Ranorex Test Automation Tools at one of these workshops.

Look at the schedules for additional workshops in the next few months.
We look forward to seeing you there!!
Categories: Companies

Mobilegeddon is here.

Google’s new algorithms for mobile search have arrived. If you’re calling it #Mobilegeddon then it caught you by surprise.  And in fact, it’s catching a lot of businesses off guard if they don’t have a solid digital performance strategy in place. A bit of background Google is in the process of changing how they rank […]

The post Mobilegeddon is here. appeared first on Dynatrace APM Blog.

Categories: Companies

Discover the “dark side” of your apps at MICROSOFT IGNITE 2015!

HP LoadRunner and Performance Center Blog - Mon, 04/20/2015 - 18:01

Ignite.pngThe Windy City is about to light up with excitement! Microsoft Ignite is infiltrating the city, and the HP team is so excited to join the excitement.


We will be discussing the “dark side” of your apps, and how you can keep your apps from going there. Keep reading to find out how to connect with the team and what we have planned for the event.

Categories: Companies

Guest Post: All About Mobile Continuous Integration

Sauce Labs - Mon, 04/20/2015 - 17:34

Image credit: Loris Grillet

CI’s not a new thing. Wikipedia says the phrase was first used back in 1994, way before modern mobile apps. Today it’s commonplace in many dev shops for developers to expect that their code is automatically tested when they commit and even automatically deployed to a staging environment.

For mobile developers though, it’s been a slow road to adopting many of these same practices.  In large part, this is because mobile brings with it a whole set of unique challenges that make implementation tough.  Nevertheless, tools have evolved a lot and mobile dev teams get a lot of value and goodness from having a solid CI system in place. Here are my top 3 reasons for using CI with the mobile products I work on:

  • No Touch Configuration: Human beings are terrible at creating releases.  They inevitably misconfigure something.  I want PROD releases to literally be a single button press.
  • Automated OTA Distribution: During development there’s always somebody that needs a new build of the app and having to manually create a build each time is super time consuming.  With CI I can press a button and have it automatically build, code sign and push them an email w/ an install link.
  • Builds And Tests: If code is committed that doesn’t compile or breaks tests I want to know ASAP.

What Makes CI for Mobile Different?

  • Infrastructure: As we all know, iOS is an huge part of the mobile ecosystem. If you’re at all familiar with iOS development then you’re almost certainly well acquainted with Xcode and I’ll bet you a warm cup of coffee you’re doing all your development on a Mac. Know how I know? Of course, you can only build (and compile) iOS applications on Mac hardware. What that means for setting up a CI system is that if you’re going to support iOS you’re going to have to get a dedicated physical Mac machine.  No EC2 for you.
  • Compilation/Code Signing: Configuring an environment to compile a mobile app is quite different than setting up CI for most web environments. There are often a number of dependencies that need to be in place to make the compile work, like Xcode or Android SDK versions. Once a compilation has completed and you’re left with an APK (Android) or IPA (iOS) file there’s a code signing step that’s required before an app can be installed on a device. This is an important and non-trivial step that has no analog in a web environment. Any CI solution that isn’t specifically designed to handle this step will not be able to produce builds that run on devices. Furthermore, since code signing certificates/keystores are sensitive pieces of data the signing process needs to be designed to protected them.
  • Testing: Testing mobile applications bears some resemblance to web testing. There are both Functional and Unit testing frameworks for iOS and Android. However, running Functional tests on a mobile application requires the use of an Emulator/Simulator or a physical device. In either case, automatically starting/stopping emulators and simulators is difficult and error prone and physical devices become bottlenecks in a hosted environment. There just isn’t a corollary to this on other platforms.
  • Deployment: Deployment for mobile typically means either distribution to testers or publishing your app to an App Store. For web developers getting your app our there is as easy as committing your code, especially if you’re doing some form of Continuous Delivery. For mobile this is a multi step process that requires building, signing and uploading your app to a service like Hockey App.

Simulators, Emulators and Real Devices

When it comes to testing mobile applications there seems to be a lot of confusion around when/how often to test using real devices vs simulators/emulators.  The actual decision regarding which to use is subject to a few variables that vary by product/team.  First, however it’s often helpful to explain the benefits and differences of each of these options.

  • Simulators vs Emulators: It’s important to note that these are not the same thing and while the Android SDKs ship with Emulators, Xcode (iOS) uses Simulators.  The biggest difference between the two is that Android Emulators actually use the same instruction set (usually ARM) that the target device uses.  On the other hand iOS Simulators run using the instruction set on your dev machine (x86).  What this means is that the same build that runs on an Android emulator will run on an actual device.  Builds compiled to run in an iOS simulator however will not run on an iOS device.  The downside to emulators is that they’re very slow while simulators are much faster.
  • Real Devices: There’s really no substitute for testing your application on the same physical hardware that your users are running.  In practice Simulators and Emulators will catch many issues but, and this is especially true w/ Android, the variations and sometimes bugs found on the devices themselves can only be found by testing w/ the actual device.  Furthermore, if your application has a reliance on specific physical hardware (i.e. Bluetooth Radio) it may be impossible to test without physical hardware.

So, when/how often should you test w/ each option?  (Disclaimer, opinions to follow)  In my experience, during the development process the variables to optimize for are speed and cost.  In other words, when your developers are committing a lot of code you want your tests to be fast and cheap.  On the other hand, when you’re getting ready to prep a release build it’s ok if your tests take longer to finish.  What’s important is that you’re getting as much coverage and accuracy as possible.  As such, my recommendation to most people is that they use simulators/emulators on their feature branches and physical devices on their master and release branches.

Tools For Mobile CI

There’s been a lot of progress over the last year or two on mobile CI tools.  Testing frameworks have come a long way and now there are a handful of hosted CI platforms designed to make setup as easy as possible.  Here are a few of my favorite tools:

  • Hosted CI Platforms:
    • The first CI solution to market focused specifically on mobile.  Ship has an easy to use setup process, and supports both Simulators and Real Devices for testing.
    • Greenhouse CI: A newcomer, also focused specifically on CI for mobile applications.  Greenhouse has a well designed UI that makes it easy to use for less technical team members.
    • Travis CI: Popular, robust CI platform with support for OSX based infrastructure.  Configuration process is driven by a YAML file so it’s a bit less friendly than the UI offered by Ship and Greenhouse.  That said, some folks prefer YAML.
  • Testing Frameworks:
    • XCTest: This unit testing framework first debuted in Xcode 5 and replaced the older OCUnit framework.  Since it’s baked right into Xcode it’s become the “default” go-to framework for many people.  XCTest has a solid feature set and is relatively straightforward to learn and start using.
    • JUnit: The corresponding “Out Of The Box” solution for Android developers. Similiarly it is tightly integrated with Eclipse and Android Studio but can also be run from the command line using Grandle or Ant.
    • Appium: Developed by Sauce Labs, Appium is a popular cross-platform framework that allows you to write tests that run on both iOS and Android.  Another big plus is that it’s based on Selenium so folks who have worked w/ this in the past will find it a familiar transition.
    • KIF: “Keep If Functional” (KIF) is an iOS-only Functional Testing framework with a strong focus on usability.  If you’re looking to write tests that reproduce user behavior at the UI-level (vs unit tests) I strongly recommend taking a look at this one.

In the end setting up CI for your mobile dev team is all about picking the right tool for the job.  There is no one-size fits all solution and the depth and complexity of your system should match the needs and budget of your team.  Large, well-funded organizations have very different engineering and business needs than small, early stage startups.  The approach that I’ve seen be the most successful is to start with obvious pain points that everyone on the team knows about and automating them on a gradual basis rather than sinking lots of time into a large, potentially unnecessary process.

-By Kevin Rohling


Kevin Rohling is the Co-Founder of Emberlight and Ex-CEO of (formerly CISimple), the first platform to offer Mobile CI as a Service.

Categories: Companies

Peripheral vision and peripheral testing

PractiTest - Mon, 04/20/2015 - 12:10

Back in high-school I was part of my school’s basketball team, and I remember that one of the first lessons I got from my coach was about the advantages of peripheral vision.

He explained to me that peripheral vision in the game was incredibly helpful as it allowed you to:
1. Look at one member of your team and pass the ball to another member, and so confuse the guys from other team while in defense.
2. It helped you to find the “open” guy in the team and pass him the ball at the right time (hopefully when he was alone under the rim).
3. And it also helped you to see if someone was approaching you in order to block you while you where trying to cover the guy dribbling the ball in front of you.

There were plenty of other things he mentioned, but the point was that he made us perform all sort of drills and practices (inside and outside of the basketball court) to help us develop our peripheral vision.

So much so that this is something that I still use today, while sometimes trying to handle my 3 kids alone, specially when we are in the mall or in the park and each of them decides to run on different direction to seek their own trills…

What is peripheral vision?

peripheral visionAlmost everyone has some level of peripheral vision, even you have it!

Have you ever notice when you are walking in the street and all of a sudden someone is running in your direction approaching you from the side?  The fact is that even if you were looking straight in front of you, you will still be able to “notice” that person, or car, or kid in the bicycle approaching you fast from the side of the street.  Basically you caught their movement with “corner of your eye”, and that is peripheral vision.

I believe that this is one of those things we should have developed some 100K years ago as part of our evolution.  Think about it, this might be the reason your great-great-great cave-dwelling grandfather did not get stomped by a big mammoth and his cousin did back in the day…

I think that some people have naturally better peripheral vision than others, but as I mentioned above, there are also drills and things you can do to enhance your peripheral vision and make it more accurate and refined.

Is there such a thing as peripheral testing?

mistakeWell, I guess if there wasn’t such a thing I would not be writing this blog, right?

Peripheral testing is the process of finding bugs and issues in your product even if you are testing other areas and aspects of it (or even if you are testing another product altogether).

Just as in the case of peripheral vision, peripheral testing is something that most testers do every day – even without noticing it.

For example, when you are are running a test flow in your product and you notice that the logo of your company on the top right section is cut.  You were expecting to find a bug in the functional flow of the application and you were not looking or expecting to find this bug, but it caught your eye and so you found it.

The problem or the challenge with peripheral testing is that sometimes or some people might miss these bugs in the product because they were not looking for them.  And I think that this is especially true for people who are only starting in testing, and also for those who tend to get “too focused” on their testing objective.

Can you develop your peripheral testing skills?


I find that there are things that will help you to develop your peripheral testing skills, some of them are easier to practice than others.

1.  Find your balance between focus and “dispersity”.  By dispersity I mean the feeling when you are looking at all places at the same time (but not focusing on anything).  By definition, in order to find the things that you are not looking for, you need to be open to find them when they appear, and this can only happen if you have room in your mind to detect them.

2. Make it a habit of “looking around” after every operation.  This is something I try to teach some of the junior testers in my teams, put aside some time during your tests to look around your testing, this is very similar to the “focus/de-focus” technique but applied on a very low level.  If you are running a functional flow that goes over a number of screen, make sure that you stop to look at the whole screen before your press the “next” button.

3. Learn to find your testing zone.   As trivial as it may sound, if you are completely concentrated on testing, and manage to leave all distractions out, you will be able to free some of your mental resources to find the stuff on the sides of your testing tasks.

4. Test twice, once for the functionality and the other one for the rest of the stuff.  This is another exercise for Junior testers, when you are running a testing operation run it twice.  The first time to test the functionality you were looking for, and the second one to see everything happening to the application while this functionality is happening.

5. Do more pair-testing.  When 2 people are looking at the same thing while it happens, there are bigger chances that one of them will “catch” things happening on the side and alert the other to them so that both of them can research this.

6. Fight your urge to “robot test”.  This is especially true for testers working on repetitive tasks, when you are running the same test for the 20th time, it is very easy to tune yourself off and let your mind wonder to any other place in the universe.  In these cases the only way you will see a bug is if it blue-screens your machine more or less…  Regardless of how many times you are tasked with running the same test you need to be on your toes and make sure to focus on the work at hand!

 And finally, there are some things that come with time

Just like good whiskey, or like pain in your joints and back when you wake up, there are some things that will come with time…

As frustrating as this may sound, peripheral testing is one of those skills that testers develop with experience and time.  The more you’ve tested, the more prone you will be to finding stuff that others simply pass over and miss completely.

Categories: Companies

Have you Crossed the Agile Chasm?

In 1991, Geoffrey Moore refined the classic technology adoption model with an additional element he called the “chasm.”[1] He advanced a proposition specific to disruptive innovation that there is a significant shift in mentality to be crossed between the early adopter and the early majority groups. Disruptive innovation is the development of new values that forces a significant change of behavior to the culture adopting it. In this case, Agile is that disruptive force that insists on applying a set of values and principles within a specific culture of “being Agile” to be successful and for the organization to realize the full business benefits of Agile.
At first glance, it would appear that many companies have adopted Agile. I believe, however, that this perception is specious, in view of the further observation that the majority of companies that are “doing” Agile have not actually adopted the new values and principles and not made the cultural shift to actually “being” Agile. Such companies look at Agile as a set of skills, tools, and procedural changes and not the integrated behavioral and cultural change it truly is. In other words, they think they have crossed the chasm, but they have not made the significant change of behavior required to make the leap. My experience in the field leads me to posit a refinement on Moore's chasm concept as applied to Agile. First, there is the real Agile chasm between those on the left side who have made the organic behavioral changes consistent with the values of being Agile―and those on the right side who are just doing” Agile mechanically. Second, there is a fake chasm, which many organizations pride themselves on having crossed by virtue of adopting some mechanical features of Agile, whereas they have not been willing or able to make the behavioral changes and adopt the values required to cross the real chasm. Although many companies say that they are doing Agile in some form, a large proportion of these are actually doing Fragile ("fake Agile") or some other hybrid variant that cannot deliver the business benefits of Agile.
I cannot overstate this point: many companies and their teams are mechanically doing some form of Agile without having actually crossed the Agile chasm, not discarding the behavioral baggage that is keeping them from behaviorally and culturally being Agile. Until a team attains the state of being Agile, the business benefits that Agile can provide will be elusive. I contend that the industry has barely entered the early majority of true Agile cultural transformation, and many companies continue to struggle to leap the Agile chasm.  What have you noticed across the Agile landscape?  Have companies crossed the Agile chasm?
Note: If you are looking for more insight in crossing the Agile chasm, consider reading the book Being Agile. This book lays the foundation for those who want to cross the Agile cultural chasm, understand the behaviors that need to change, and gauge progress along the way. It provides an Agile transformation roadmap to the destination of achieving better business results.

[1] Geoffrey A. Moore, Crossing the Chasm (New York: Harper Business Essentials, 1991).
Categories: Blogs

Testomato monitors your website and alerts you if anything important breaks - Fri, 04/17/2015 - 23:00
Monitor both your staging and production environments to catch problems immediately. Instead of worrying, know when something is broken so you can fix it fast.
Categories: Communities

uTesters: Be Our Facebook Cover Photo

uTest - Fri, 04/17/2015 - 18:02

IMG_5071 You don’t have to be uTesting from a mountain or even from a hammock outdoors (although that sounds quite relaxing right now…). We want to see you as you uTest in your natural habitat…wherever that is…as part of our new weekly contest through the end of May!

By posting your best photo(s) to our Facebook page, the uTest Community Management team will select one favorite entry that will become the uTest Facebook’s cover photo for the week!

Not only will your testing scene be in all it’s glory in front of our nearly 36,000 testers that have ‘liked’ our page, you’ll also receive a uTest swag pack full of uTest gear including t-shirts, pens, and other goodies we can’t yet reveal.

The Rules & Timeline:

  1. Like our uTest page on Facebook (many of you have already!).
  2. Take a picture of you, or have someone take a picture of you, while you are testing with uTest (Note: Pictures cannot contain proprietary customer information and must be at least 851 pixels wide by 315 pixels tall)
  3. Post the photo or photos to our Facebook timeline each Friday by 9am Eastern Time. You must have a registered account with us.
  4. Check back soon after as we will be selecting one winner and making them our cover photo for the week (and contacting them for their swag pack)!
  5. We’ll be running this contest each week through May, so enter once every contest period if you’d like!

Post your photo to our Facebook timeline now!

The post uTesters: Be Our Facebook Cover Photo appeared first on Software Testing Blog.

Categories: Companies

Saga Implementation Patterns: Singleton

Jimmy Bogard - Fri, 04/17/2015 - 17:38

NServiceBus sagas are great tools for managing asynchronous business processes. We use them all the time for dealing with long-running transactions, integration, and even places we just want to have a little more control over a process.

Occasionally we have a process where we really only need one instance of that process running at a time. In our case, it was a process to manage periodic updates from an external system. In the past, I’ve used Quartz with NServiceBus to perform job scheduling, but for processes where I want to include a little more information about what’s been processed, I can’t extend the Quartz jobs as easily as NServiceBus saga data. NServiceBus also provides a scheduler for simple jobs but they don’t have persistent data, which for a periodic process you might want to keep.

Regardless of why you’d want only one saga entity around, with a singleton saga you run into the issue of a Start message arriving more than once. You have two options here:

  1. Create a correlation ID that is well known
  2. Force a creation of only one saga at a time

I didn’t really like the first option, since it requires whomever starts to the saga to provide some bogus correlation ID, and never ever change that ID. I don’t like things that I could potentially screw up, so I prefer the second option. First, we create our saga and saga entity:

public class SingletonSaga : Saga<SingletonData>,
    protected override void ConfigureHowToFindSaga(
    	SagaPropertyMapper<SingletonData> mapper)
    	// no-op

    public void Handle(StartSingletonSaga message)
        if (Data.HasStarted)

        Data.HasStarted = true;
        // Do work like request a timeout
        RequestTimeout(TimeSpan.FromSeconds(30), new SagaTimeout());
    public void Timeout(SagaTimeout state)
    	// Send message or whatever work

Our saga entity has a property “HasStarted” that’s just used to track that we’ve already started. Our process in this case is a periodic timeout and we don’t want two sets of timeouts going. We leave the message/saga correlation piece empty, as we’re going to force NServiceBus to only ever create one saga:

public class SingletonSagaFinder
    : IFindSagas<SingletonSagaData>.Using<StartSingletonSaga>
    public NHibernateStorageContext StorageContext { get; set; }

    public SingletonSagaData FindBy(StartSingletonSaga message)
        return StorageContext.Session

With our custom saga finder we only ever return the one saga entity from persistent storage, or nothing. This combined with our logic for not kicking off any first-time logic in our StartSingletonSaga handler ensures we only ever do the first-time logic once.

That’s it! NServiceBus sagas are handy because of their simplicity and flexibility, and implementing something a singleton saga is just about as simple as it gets.

Post Footer automatically generated by Add Post Footer Plugin for wordpress.

Categories: Blogs

NCover Updates For Desktop & Bolt

NCover - Code Coverage for .NET Developers - Fri, 04/17/2015 - 15:01

ncover_product_update_blogWe have released several important NCover updates during the months of March and April. These updates reflect improvements across the entire product line with a heavy emphasis on NCover Bolt and NCover Desktop. The current version is V5.0.2953.994. A full list of what is included can be found on our Release Notes page. We recommend all users upgrade immediately to benefit from these improvements.  All NCover users with a current subscription can receive these updates at no charge.

Improved Bolt Performance & Stability

This release contains over a dozen individual fixes with major improvements in Bolt start-up time, resource usage, performance and general stability and reliability. All users of Bolt, NCover’s Visual Studio extension, will benefit from significant speed improvements during the preparation of test runs and the loading of tests, the collection of coverage data and post-run aggregation. In addition, we have made several fundamental changes to improve its stability and reliability when handling large test runs.

Updates to Bolt User Interface

There are also multiple improvements to the Bolt user experience, including improved feedback during collection. Users will receive additional and more detailed feedback regarding the status of Bolt, the status of test runs and when exceptions occur.

Code Central Detailed HTML Report

This release implements a fix to better handle executions with duplicate modules. Users of Desktop and Code Central can now generate, either through the command line or the GUI, a summary HTML report.  Code Central users can also generate a fully self-contained HTML report that can be distributed across teams or to other individuals. You can review available options for sharing coverage results in Code Central here.

Improved Stability For Multiple App Domains

There’s now improved reliability for applications that use multiple app domains, and a fix for isolated cases that resulted in dropped coverage. If you have any questions about your specific situation, or are interested in best practices for working with multiple app domains, please do not hesitate to contact us.

Over 47 Individual Fixes, Additions and Enhancements

We have been extremely busy improving the Bolt and Visual Studio experience and implementing user requests.  We appreciate all of the feedback our customers have provided and we believe you will be pleased with the results in the latest version of NCover.

As a reminder, the easiest way to update your install of NCover is either with the auto-update feature or through the Visual Studio gallery update.  If you need any assistance with your upgrade, please submit a technical support request and we will be happy to walk you through the process.

The post NCover Updates For Desktop & Bolt appeared first on NCover.

Categories: Companies

Knowledge Sharing

SpiraTest is the most powerful and affordable test management solution on the market today