Bug Blog

UAT isn’t always easy. User acceptance testing can sometimes be costly. Acceptance tests take a long time to write and, once implemented, they take a long time to run. User acceptance testing cannot move forward any faster than the speed of the user. UAT can also be expensive to maintain, because it is so intimately tied to user experience. Every change, even the simple renaming of a button, requires updating the tests. Consequently, there is a strong tendency to minimize acceptance testing in order to speed delivery and save money. But is this really a good idea? While user acceptance testing can be a pain, it does have its benefits.

There has been considerable change in software development over the last decade. New methods have been worked out in an attempt to shorten development time and contain costs, some of these include the spiral model, dynamic systems development, rapid application development, and of course agile software development.

Testing is a vital part of software development. Whether testing is done manually or through the use of automation, depends on the circumstances. The choice can be influenced by such things as the project's requirements and the expertise available. However, it usually comes down to some combination of time and money. Like it or not, cost reduction and speed of delivery are both important parts of software development. So, knowing when to test manually and when to use automation can have a considerable effect on the bottom line and the final outcome.

Accessibility is the concept of ensuring that everyone can equally use a particular digital asset, whether it is a website or an application. It is more than just making sure that people who are physically challenged have equal access. True accessibility benefits everybody. It benefits both the user and the developer by providing access to digital resources in multiple ways. And the path to accessibility lies in the understanding of universal design.

Software testing can be a rather formalized procedure. And while formal processes are important it is impossible to develop procedures that will always successfully find bugs. The very nature of coding and the complexity of software development makes this impossible. So there comes a time when formalized testing must be set aside. It is these times when the software tester’s skill is most evident.

Agile programming allows for faster delivery while providing greater opportunity to enhance quality. Agile does this through a methodology that operates in increments or iterations that are referred to as sprints.

Bugwolf has the honor of being chosen to pitch in a “Shark Tank” style presentation, along with a select group of other startups, at the CIO Edge Summit on Tuesday the 11th of October. The CIO Edge Summit will take place at the St. Regis in Singapore.

Good software development begins with good documentation, in fact, the better the documentation the faster and smoother the development cycle will be. Documentation isn't just working out stakeholder requirements. Ideally, it's taking the guesswork out of the development cycle, at least as much as possible. The more established the documentation, the easier it will be for the different subgroups engaged in development to operate as a team.

The increased importance of mobile interaction is in the process of turning apps into important sales and business tools. As businesses develop mobile strategies, the desire for creating mobile apps that fulfill all the necessary interoperability, offline capability and security requirements needed to enable business to operate in a mobile friendly manner continues to climb. It then becomes a matter of deciding which is best, hybrid or native apps.

The purpose of starting lean in software development is to meet the customer's requirements as quickly, effectively and economically as possible. The idea is to keep things simple and practical. Waste and unnecessary actions are eliminated and each part of the development cycle has its own sub goals leading to the final product.

We human beings like to break everything down into patterns. The idea being that if you follow the same pattern you will always get the same result. This isn't always true. In software testing, there's simply too many variables for their to be a one size fits all, paint by numbers, system that will always find every bug.

The first step in getting the most for your software testing dollar is to make certain that any bugs found are followed up on. Simply documenting failures isn't enough, a good tester will work hard to find the root cause of any failure. So, don't just look for pass or fail, look for the reason why.