Skip to content

Feed aggregator

Continuous delivery requires automation, collaboration

Kloctalk - Klocwork - Tue, 04/15/2014 - 15:00

Evolving end-user expectations are forcing companies to rethink their application development and deployment strategies, largely because launching inefficient or vulnerable software can result in significant financial and reputational issues. Witnessing major corporations encounter massive breaches and other incidents because of inadequate software is a wake-up call for most enterprises and is driving decision-makers to embrace continuous delivery initiatives that reduce the chance of pushing out incomplete applications.

Unlike conventional application development processes, continuous delivery programs focus on improving collaboration between developers and operations teams, utilizing automation and using early feedback to eliminate issues before the final product is released. A recent Perforce report highlighted some of the best practices that go into establishing a continuous delivery strategy, such as tracking every change made throughout development, which can make it easier for employees to revert to prior models if an unforeseen technical hurdle emerges down the road.

"Companies can no longer afford to wait until the end of long development and release cycles to find out if they're keeping up with market demands," said Christopher Seiwald, founder and CEO of Perforce Software.

Among the many practices that go into building a comprehensive and effective continuous delivery strategy is automation – the key to speeding up delivery without compromising quality.

Automation is a must
One of the many problems with conventional software development programs involved the constant challenges that emerged due to human error. In the past, every step of the process – including testing – was completed by a person, which meant small oversights could inadvertently create monumental performance issues once the product was released.

Experts highlighted the importance of using automated technologies to mitigate the errors of individuals implementing changes that would lead to problems down the line. Additionally, automation means a single task is not unnecessarily repeated. Static analysis solutions can quickly run through code to detect anomalies and other issues that could compromise the overall effect of the platform. 

Support collaboration
In addition to the unnecessary presence of human input, conventional development processes were generally segmented, which impaired the overall flow when creating applications. Executives who want their teams to build and launch the most effective and rewarding platforms need to knock down traditional silos and ensure developers, quality assurance personnel and other individuals involved with application development can easily communicate and share information.

Sophisticated code review technologies can make this collaborative endeavor easier by enabling employees to analyze software throughout its development process. Rather than encouraging individuals to work on a single task at any given time, adopting DevOps and other emerging philosophies that allow multiple eyes to evaluate code gives firms the ability to produce software that has a lower risk of housing a vulnerability upon release.

The expanding mobile landscape is putting an immense amount of pressure on the development environment, as both businesses and consumers use mobile-enabled applications frequently and for more purposes. If those individuals end up utilizing insecure or inefficient solutions, organizations may face unwanted brand reputation or financial problems.

Categories: Companies

Ranorex 5.0.2 Released

Ranorex - Tue, 04/15/2014 - 10:00
We are proud to announce that Ranorex 5.0.2 is now available for download. General changes/Features
  • Added support for Firefox 29
  • Added "durationms" field to report activity XML nodes and a "timestampiso" (ISO8601) timestamp field to the report root activity XML node
Please check out the release notes for more details about the changes in this release.

Download Ranorex version here.
(You can find a direct download link for the latest Ranorex version on the Ranorex Studio start page.)

Categories: Companies

SonarQube 4.2 in Screenshots

Sonar - Tue, 04/15/2014 - 08:07

The team is proud to announce the release of SonarQube 4.2, which includes many exciting new features:

  • Multi-language analysis
  • Tags of rules
  • New visual measure filter representations (bubble chart, pie chart and histogram)
  • Improved Issues page

Multi-language Analysis

The most voted JIRA ticket ever is now fixed! Running an analysis on a multi-language project is now rather simple. Just point to the parent directory containing all the source code and that’s it. Then, from the very same place, you can browse issues on all your files whatever their language.

Tags of Rules

Thanks to the tagging mechanism, you can now classify coding rules, which should ease searching.

New Visual Measure Filter representations

Bubble chart, pie chart and histogram are now available to display your filters in nice and meaningful ways.

Improved Issues Page

The Issues page was redesigned to make it easier to search for and browse issues.

That’s all, Folks!

Time now to download the new version and try it out. But don’t forget to read the installation or upgrade guide.

Categories: Open Source

Testing on the Toilet: Test Behaviors, Not Methods

Google Testing Blog - Mon, 04/14/2014 - 23:25
by Erik Kuefler

This article was adapted from a Google Testing on the Toilet (TotT) episode. You can download a printer-friendly version of this TotT episode and post it in your office.

After writing a method, it's easy to write just one test that verifies everything the method does. But it can be harmful to think that tests and public methods should have a 1:1 relationship. What we really want to test are behaviors, where a single method can exhibit many behaviors, and a single behavior sometimes spans across multiple methods.

Let's take a look at a bad test that verifies an entire method:

@Test public void testProcessTransaction() {
User user = newUserWithBalance(;
new Transaction("Pile of Beanie Babies", dollars(3)));
assertContains("You bought a Pile of Beanie Babies", ui.getText());
assertEquals(1, user.getEmails().size());
assertEquals("Your balance is low", user.getEmails().get(0).getSubject());

Displaying the name of the purchased item and sending an email about the balance being low are two separate behaviors, but this test looks at both of those behaviors together just because they happen to be triggered by the same method. Tests like this very often become massive and difficult to maintain over time as additional behaviors keep getting added in—eventually it will be very hard to tell which parts of the input are responsible for which assertions. The fact that the test's name is a direct mirror of the method's name is a bad sign.

It's a much better idea to use separate tests to verify separate behaviors:

@Test public void testProcessTransaction_displaysNotification() {
new User(), new Transaction("Pile of Beanie Babies"));
assertContains("You bought a Pile of Beanie Babies", ui.getText());
@Test public void testProcessTransaction_sendsEmailWhenBalanceIsLow() {
User user = newUserWithBalance(;
new Transaction(dollars(3)));
assertEquals(1, user.getEmails().size());
assertEquals("Your balance is low", user.getEmails().get(0).getSubject());

Now, when someone adds a new behavior, they will write a new test for that behavior. Each test will remain focused and easy to understand, no matter how many behaviors are added. This will make your tests more resilient since adding new behaviors is unlikely to break the existing tests, and clearer since each test contains code to exercise only one behavior.

Categories: Blogs

Selenium For Pythonistas

Testing TV - Mon, 04/14/2014 - 22:01
If you’re a full-stack Python developer who wants to incorporate functional tests into your toolkit, this presentation is aimed at helping you understand the why and when of Selenium. Learn about writing robust and maintainable tests for your web apps that can be run in any continuous integration setup. Video producer:
Categories: Blogs

Good News For Aspiring App Designers

uTest - Mon, 04/14/2014 - 18:57

marvel_appJust when you thought the mobile app world couldn’t get any more crowded and competitive, along comes Marvel.

The UK startup has come up with a new iPhone app that can turn the average person into a web or mobile-app designer, regardless of design and technical skill. With no coding required, users can easily turn their concept into an interactive prototype, and share it with friends, clients, coworkers, or through social media.

To the seasoned app designer, this might seem like amateur hour. But here are 4 reasons why this has the potential to gain momentum and completely alter the software design (and therefore testing) world.

1. It’s extremely easy.
Draw your screen ideas on a piece of paper, take pictures of the wireframes and use the Marvel app to apply “touch” hotspots to the image. Apply links to screens in order indicate how you would like to app to be navigated and boom – you have a touchable, interactive prototype.

“In the past, if you wanted to see your app or web designs and ideas in anything more engaging than PDFs and PowerPoints, you needed to have the skills and the time to code it into an interactive prototype,” explains Marvel co-founder Murat Mutlu. Now, all you need is this app on your smartphone.

2. It turns the average person into a designer, and reaches a wide audience.
Remember when Instagram turned the average person into a photographer? Users could process high quality photos without needing an expensive camera or experience. People who had never edited a picture before were suddenly part of the craze.

Similarly, Marvel hopes to inspire individuals to “pick up and play” with the app and attract non-designers to give it a try.

Co-founder of Instagram, Kevin Systrom, attributes the success of Instagram to its ability to appeal to a wide audience of individuals and companies alike.

“Instagram is not a market for selling [photography] but I’ve seen an amazing amount of people using their account to promote their business. That’s been inspiring to me.”

Marvel also offers just that. It allows companies to design, review, and test prototypes without writing a single line of code, saving time and money.

3. Shareable and useful for feedback.
Connect to DropBox and start your first project. Once you’re finished, share it using a URL with your clients, teams, or even friends through email, Facebook, Twitter, or text. Since the prototype can be navigated as if it is an actual app, it is great for user feedback.

Marvel currently offers a free service but plans on offering a Premium model that offers other service integrations like team collaboration.

4. Maintain your originality.
Get a leg up on a new wave of mobile app designers with your Photoshop skills. Rather that offering cookie-cutter models that could potentially make every web and mobile app look the same, open your screen images up in Photoshop, make design changes, and share the PSD file to DropBox.

Marvel is not the only company which offers this type of prototyping service. Apps like InVision, which are also supported by DropBox, also have significant funding and headway as well. So although it’s hard to say what company will come out on top, it’s safe to say that app design world is about to become more dynamic and competitive, and the software testing world will have a lot more work to do.

As a tester, what do you think about the “average” person suddenly becoming a mobile app designer? Be sure to share your thoughts in the comments section below.

Categories: Companies

Preparing for Load Testing Best Practices

Software Testing Magazine - Mon, 04/14/2014 - 18:34
It has been put in evidence by some famous recent failures that load testing is an important activity when you release a public web site. This article provides some hints and tips hat will allow you to prepare for successful load tests.  These load testing best practices range from working with the right team to collecting the meaningful metrics. Andrew Smith, BugHuntress, Being an integral part of every development effort, load testing aims to define the limits and capacity of the application by putting demand on a system and measuring its ...
Categories: Communities

Don’t Miss the Gain and Engage Users Workshop on April 25

Sauce Labs - Mon, 04/14/2014 - 18:30

San Francisco App Strategy Workshop  Optimization   DevsBuild.ItIf you missed out on tickets to the Front End Ops Conference, never fear: we have another fantastic event for you!

Sauce Labs’ Mark De Visser will be speaking about testing and performance at 11:30 AM on Friday, April 25 in San Francisco at the Gain and Exchange Users Workshop by the Application Developers Alliance.  He’ll be speaking along side folks from New Relic, AT&T, Open Table, and more.

For more about the event, see below:

Join developers, analytics experts, and leading app publishers and platforms to learn about tools and strategies to understand your users, boost retention, and drive downloads. Take a deep-dive into app store optimization and explore ways to get your app discovered.

The Gain & Engage Users Workshop is part of a nationwide App Strategy Workshop series complete with 15 events. Click here for event information and to view related videos.

Check out the rest of the schedule and register here. Don’t miss this great workshop – it’s the furthest $10 will ever get you in San Francisco!

Categories: Companies

Can software-powered ships pass the test when it comes to reliability?

Kloctalk - Klocwork - Mon, 04/14/2014 - 15:35

In the wake of developments in the areas of self-driving cars and unmanned aerial drones, new software-driven vehicles may soon be coming to the sea as well as land and air. Rolls-Royce Holdings recently announced that it is developing unmanned drone ships in an attempt to cut costs and pollution in the $375 billion overseas shipping industry that accounts for around 90 percent of world trade. At the same time, the move will face considerable regulatory hurdles, and, similar to the push toward self-driving cars, important questions about the reliability of on-board systems.

The push for unmanned ships makes sense, according to Rolls-Royce, which notes that crew costs currently amount to around 44 percent of total operating expenses for a large container ship. In addition to cutting these costs, replacing many of the crew facilities on the ship could add more space for cargo, reduce ship weights by around 5 percent and cut fuel use by 12 to 15 percent, Oskar Levander, the company's vice president of innovation in marine engineering and technology, told Bloomberg. The plans would entail ships being manned from remote, on-land control centers, similar to aerial drones.

"Now the technology is at the level where we can make this happen, and society is moving in this direction," Levander told the publication. "If we want marine to do this, now is the time to move."

Right now, unmanned ships are illegal under international rules that set requirements for minimum crews, according to Simon Bennett, a spokesman for industry association International Chamber of Shipping. He told Bloomberg that the organization is not seriously considering the issue, and a spokeswoman for the International Maritime Organization said it had not received any proposals yet on unmanned ships. The International Transport Workers' Federation, a union that represents around 600,000 sailors worldwide, criticized the initiative, noting that a human element was the first line of defense against mechanical failures and the sudden changes the sea could entail.

Making it reliable
Levander noted that unmanned ships will need to have extensive monitoring systems and plenty of redundancies. He added that data from cameras and sensors can be used to improve performance, and, in cases such as detecting obstacles, are already more effective than the human eye.

"It's a given that the remote-controlled ship must be as safe as today," he told Bloomberg. "But we actually think it can be even much safer than today."

In an article for IEEE Spectrum, contributor Evan Ackerman argued that much of the current risk in maritime accidents stems from humans themselves, and he suggested that software could make ships much safer and more reliable, in part because - at the very least - computer errors occur in predictable patterns. He compared the initiative to self-driving cars and argued that the ocean could probably be modeled as accurately as the chaos of rush hour traffic, for instance.

"We just have to get over the knee-jerk reaction that humans can do a better job at it than an autonomous system," he wrote.

Winning that battle of perceptions won't be easy: Self-driving cars have been the subject of protracted legal debates and still appear to be years away from effecting any sort of regulatory changes, despite a long development history. In part, regulators will want to be assured that software is error-free. As companies develop unmanned projects of any kind, including ships, the use of source code analysis tools to catch and eliminate errors will be essential in generating public approval, as well as in preparing for compliance with any future coding standards. And in any instance of new ways to apply software to the physical world, new regulatory frameworks and coding standards are almost a given.

For the time being, the prospect of drone ships may still be a long way away, though. Levander told Bloomberg that his comments at an industry conference last year were widely dismissed, but he also noted that unanimous support wasn't necessary for change to begin to happen. Ackerman noted that the transition would likely follow the course of Google's experiments with self-driving cars, requiring a human presence on board ships while teleoperation functions were tested. Regardless of what happens next, the Rolls-Royce announcement could be an important step in improving software adoption in various industries.

Software news brought to you by Klocwork Inc., dedicated to helping software developers create better code with every keystroke.

Categories: Companies

SoapUI 5.0 Provides REST Mocking & Discovery

Software Testing Magazine - Mon, 04/14/2014 - 14:23
The version 5.0 of SoapUI 5.0 has just been released. SoapUI is an open source cross-platform Functional Testing solution. With an easy-to-use graphical interface, and enterprise-class features, SoapUI allows you to easily and rapidly create and execute automated functional, regression, compliance, and load tests. In a single test environment, SoapUI provides complete test coverage and supports all the standard protocols and technologies. The three main features of SoapU 5.0 are: OAuth 2.0 support, REST Mocking and REST Discovery! Since the September 2013 release of SoapUI 4.6, starting the REST in Progress ...
Categories: Communities

Resource Article on Covering IIS and Web Apps

NCover - Code Coverage for .NET Developers - Mon, 04/14/2014 - 14:14

Covering IIS and Web AppsCollecting code coverage on your web apps is crucial as part of both the development and QA process for any .NET team.  NCover’s approach for collecting code coverage allows you to perform both automated and manual tests and aggregate that collection regardless of how you like to test your web apps.  The key to this approach is setting up a project and using pre-coverage filters.

Specifically, NCover watches the w3wp.exe, the IIS worker process, in order to collect coverage. This approach allows you to automatically capture coverage once you have properly configured your project.

If this is your first time covering IIS with NCover, you may find the “auto-configure” method the easiest.  If you are experienced, you may prefer the manual approach.

The three-step process for covering IIS with NCover can be found at

If you have any questions with getting setup, please feel free to contact technical support.

The post Resource Article on Covering IIS and Web Apps appeared first on NCover.

Categories: Companies

Agile Lagging to Leading Metric Path

Even in an Agile environment there is a benefit to applying measures to understand progress.  It can be tempting to apply the same iron triangle metrics (based on cost, schedule, and scope) that may have been used in a more traditional mindset to Agile projects and initiatives.  Instead, I suggest removing all of those metrics and start with a clean slate.  On the clean slate, consider your outcomes.

An Agile mindset asks that you consider outcome instead of output as a measure of success.  This means we should first start with understanding our desired outcomes for an initiative or project.  Within a business context of building products, one measure of success an increase in revenue. Having a customer revenue metric helps you understand whether the products being built are increasing revenue upon release. While capturing revenue is a good starting point, it is a “lagging” indicator meaning you don’t recognize the evidence of revenue movement until after the release is in production and has been in the marketplace for a period of time.
To supplement lagging measures, you need corresponding leading measures and indicators that provide you with visibility during development to gauge if you are moving the product into a position of increased revenue. I call this framework the Lagging to Leading Metric Path.  This visibility is important because it provides input for making decisions as you move forward. Making the right decision leads to improved results. As you consider measures, think about how they help you gain visibility and information for decisions in building a product that helps you lead toward an increase in revenue.
For a hopeful increase in customer revenue, what leading metrics can we put in place to ensure we are moving in the right direction?  Let’s say in this case that increased revenue is the hopeful lagging metric based on expected customer sales.  Examples of leading measures or indicators to achieve an outcome of this lagging metric for increased customer revenue include:
  • Customers attending Sprint Review: a leading metric where you capture how many customers are actually attending the sprint review and how much feedback they give. This indicates engagement and interest. 
  • Customer satisfaction from Sprint Review: a leading metric is capturing customer satisfaction from the functionality they viewed within the sprint review.  This indicates levels of satisfaction with the functionality as the product is being built. 
  • Customer satisfaction of product usage: an indicator of the most recent release highlighting a level of satisfaction on the usage of the current product including commentary.   

When applying Agile to product development, the outcome that matters most are often represented by lagging metrics.  Therefore you will need leading indicators to ensure you are moving in the right direction, to provide visibility, and to help you with decision-making.   Within your own context, consider constructing a lagging to leading metric path so that you know you are moving in the right direction during your Agile journey.

Note: the lagging to leading metric path really isn't specific to Agile and I would suggest applying this to an initiative or project aligning with any mindset, process, method, or practice of delivering value.

To read more about establishing an Agile Lagging to Leading Metric Path and Agile Measures of Success, consider reading Chapter 14 of Being Agile
Categories: Blogs

Variable Testers

James Bach's Blog - Sun, 04/13/2014 - 23:55

I once heard a vice president of software engineering tell his people that they needed to formalize their work. That day, I was an unpaid consultant in the building to give a free seminar, so I had even less restraint than normal about arguing with the guy. I raised my hand, “I don’t think you can mean that, sir. Formality is about sameness. Are you really concerned that your people are working in different ways? It seems to me that what you ought to be concerned about is effectiveness. In other words, get the job done. If the work is done a different way every time, but each time done well, would you really have a problem with that? For that matter, do you actually know how your folks work?”

This was years ago. I’m wracking my brain, but I can’t remember specifically how the executive responded. All I remember is that he didn’t reply with anything very specific and did not seem pleased to be corrected by some stranger who came to give a talk.

Oh well, it had to be done.

I have occasionally heard the concern by managers that testers are variable in their work; that some testers are better than others; and that this variability is a problem. But variability is not a problem in and of itself. When you drive a car, there are different cars on the road each day, and you have to make different patterns of turning the wheel and pushing the brake. So what?

The weird thing is how utterly obvious this is. Think about managers, designers, programmers, product owners… think about ANYONE in engineering. We are all variable. Complaining about testers being variable– as if that were a special case– seems bizarre to me… unless…

I suppose there are two things that come to mind which might explain it:

1) Maybe they mean “testers vary between satisfying me and not satisfying me, unlike other people, who always satisfy me.” To examine this we would discover what their expectations are. Maybe they are reasonable or maybe they are not. Maybe a better system for training and leading testers is needed.

2) Maybe they mean “testing is a strictly formal process that by its nature should not vary.” This is a typical belief by people who know nothing about testing. What they need is to have testing explained or demonstrated to them by someone who knows what he’s doing.






Categories: Blogs

Would You Like to Become an Authority on App Testing?

Testlio - Community of testers - Sun, 04/13/2014 - 11:53

You don’t need anyone to remind you that the world is going mobile. Big businesses, small mom and pop shops, solo entrepreneurs -- people from every market are developing mobile apps.
Unfortunately, a lot of the apps, even good ones, have too many bugs. Even a few small glitches can ruin an app’s reputation. Companies care about mobile testing, but many of them aren’t very good at it. They need your help. Write blog posts

Here at Testlio, we believe that mobile testing needs to be held to a higher standard. You, our wonderful testers, have proven that you’re the best in the world at what you do. However, we want to help even the people who don’t work directly with us. We want to help everyone make better mobile apps.

We’re going to do this by providing free blog articles that teach people how to be an all-star app tester, like you. Here’s how you can get involved.
We’re looking for talented app testers to share their knowledge on our blog. As you know, they don’t teach you app testing in school (though they should). There are a lot of people who don’t know what they’re talking about, and we want to help them become like you -- the best testers in the world.

What’s In it For You

As a Testlio writer, your work will be in front of the entire mobile testing community. If you write killer articles, you’ll quickly become recognized as one of the top experts on mobile testing. You've already got a huge audience. In almost exactly a year, we’ve grown to almost 2,000 passionate testers from all over the world. That number is only going to get bigger, which means more and more people are going to see you as an expert. As an added bonus, you’ll also learn some of the techniques and tricks that we use to make app testing more efficient. To get involved, leave a comment below with one of the following:

  • Your biggest question about mobile app testing.
  • Your best tip for people interested in becoming a professional mobile app tester.
We’ll pick the best responses and contact you about joining the Testlio team. Good luck!

Categories: Companies

Exploratory Tumbling

Hiccupps - James Thomas - Sat, 04/12/2014 - 07:43
A short questionnaire:

1. Do you ever find yourself navigating unfamiliar territory in search of areas that return some value?
2. Are you a bacterium?

If your answers were (no, no) or (yes, yes) feel free to stop reading now.

I was listening to a podcast, The Biology of Freedom, from the BBC's Discovery programme this week. Towards the end they talk about how cells move around seeking food using a kind of targeted random walk.

It's called chemotaxis:[a bacterium's] movement will look like ... relatively straight swims interrupted by random tumbles that reorient [it] ... By repeatedly evaluating their course ... bacteria can direct their motion to find favorable locations with high concentrations of attractantsA short questionnaire:

1. Would you be interested in a heuristic that might help guide your exploration?
2. Are you a tester?

If your answers are (yes, yes) there might be the germ of an idea for you here.Image:
Categories: Blogs

Community Update 2014-04-11–#webdev, #aspnet, #dotnet, #python for #visualstudio, #azure #webjobs

Decaying Code - Maxime Rouiller - Fri, 04/11/2014 - 23:08


Must Read/Watch

Roslyn (.NET Compiler Platform) As Open Source - Leaning Into Windows (

Banking Example Again | Greg Young's Blog on (

The story behind the wallpaper we'll never forget ( – The history behind the Windows XP wallpaper.

Web Development

How to make an Object inherit from a Class in JavaScript – Max Schmitt (

How to follow the Google webmaster guidelines (

Coherent Labs » Announcing Unreal Engine 4 and CRYENGINE integration ( – Unreal engine with HTML5 and JavaScript

Implementing Private and Protected Members in JavaScript — Philip Walton (

ColorBrewer: Color Advice for Maps (

Debugging Asynchronous JavaScript with Chrome DevTools - HTML5 Rocks (

jQuery Conf Video: Understanding Scope in JavaScript - Quick Left Boulder Colorado (

Improve your JavaScript with Web Essentials and JSHint (

Offline.js – Handle your users losing their internet connection like a pro (


Python Tools for Visual Studio 2.1 Beta (


Prototype Members vs Static Members vs Instance Members (and Dependency Injection) (

Micro-JSON - a JSON parser for the .Net Micro Framework (

Async Processing in EF6 and the Microsoft .NET Framework 4.5 -- Visual Studio Magazine (

A new search experience on the Gallery (


Intellisense for JSON Schema in the JSON Editor (

Windows Azure

Azure WebJobs 104 - Hosting and testing WebJobs in .NET with the WebJobs SDK with Pranav Rastogi (

Categories: Blogs

Jenkins 1.532.3 LTS is released

The final LTS release of the 1.532.x line is out today. You can download it from the usual location. Changelog is here.

Starting with the next 1.554.x LTS, the release model will switch to the train model, where we commit to dates and get whatever we can ship by that date.

You can see the scheduled dates in our event calendar. Backporting window for 1.554.1 is almost closing, so if you want to have your favorite issues nominated for it, please see the process in the Wiki and hurry!

Categories: Open Source

InfoQ CI survey 2014

InfoQ has been running a CI server survey for more than a month now, and here is the current result:

Jenkins has gotten more than 70% of the votes, once again proving the wide adoption among developers. If you are one of those who picked Cruise Control into the "considering" section, I'd encourage you to look around a bit more.

You can still vote from their website or leave comments if you want.

By the way, the design of two axes make no sense to me; for example, I'd order the adoption axis to "considering -> migrating to -> using now -> moving away from", and the circle seems to imply two axes are somehow interchangeable, when it should probably be just in a checkerboard to indicate those are independent axes.

Categories: Open Source

App Quality at the Center of Amazon’s AppStore Milestone

uTest - Fri, 04/11/2014 - 21:10

amazon-icon-final-large-512512Perhaps lost amidst the release of the new Fire TV, Amazon also announced that its app store has surpassed the 200,000 apps mark. The Amazon AppStore has shown significant growth since its inception just over 3 years ago. In fact, just last August the app store reached 100,000 apps; meaning that it has doubled in size in less than a year. Of course, this still pales in comparison to the Google Play and Apple App Store which both have over 1 million apps. However, Amazon is clearly becoming a larger player in the app market that developers must pay attention to.

While Amazon is certainly pleased with the overall number of apps available in the store, the company is also making a push to improve quality as well. Amazon’s AppStore Developer Select offers developers incentives for optimizing their applications specifically for Amazon devices. The benefits include preferred placement within the app store and 500,000 ad impressions. To qualify, developers must make sure their app runs in HD, taking up the entire screen, and use Amazon’s own API.

This program serves as a great reminder for developers that they must optimize their apps across a wide spectrum of devices. For Amazon specific apps, this means taking into account Amazon’s own Fire OS, several generations of Kindle tablets from the new Fire HDX to older devices, and different screen sizes including 7 and 8.9 inch models. Add this on top of Apple and other Android devices and you are looking at a diverse range of devices that need to be taken into consideration when testing.

Categories: Companies

Knowledge Sharing

Telerik Test Studio is all-in-one testing solution that makes software testing easy. SpiraTest is the most powerful and affordable test management solution on the market today