Testing Accounting Software – Account Reconciliation

XBOSoft Testing Accounting Software - Account ReconciliationThe complexity of account reconciliation software places special demands on the testers of account reconciliation software. The primary challenge: There are two types of accounts to be reconciled, each with its own unique characteristics.

IOT Quality Challenges

As I start to think about my talk on IoT Quality Challenges at The Practical Software Quality and Testing Conference in August, it’s hard not to think about IoT without thinking about wearables. Wearables are just one facet of IoT, but for the average Joe not involved in industrial IoT, wearables hit you in the face.

Requirements-Based Testing

We had a question come in during one of our webinars on test cases, and thought it deserved more thought than a simple answer within the webinar itself. The question was, "In reference to writing unit tests for requirements, requirements should be testable, but why not write the test when you write the requirement. Is that over bearing?"

Implementing Pairwise Testing – Discussions with AQAA

After my talk on Implementing Pairwise Testing at the Atlanta Quality Assurance Association last week, I had a chance to sit down and think about the discussion and the audience:

  • Great interest in tools. Everyone wanted to know how can I do it! Of course we all do, and I hope that I gave them plenty of references and sources for this.
  • Limited knowledge of a much larger field called combinatorial testing (of which pairwise testing is just a subset). . .

Using Pairwise Testing – When and Why?

I've been invited to give a talk on Pairwise Testing Test Case Design in Atlanta on August 11 for the Atlanta Quality Assurance Association. My preparation, though, involves much more than just explaining pairwise testing. When using pairwise testing as a combinatorial method for test case selection, you need to think about much more than choosing what tool to use or how it works, but rather when, where and most importantly, WHY? Why choose pairwise versus 3-wise, or 4-wise? First I had to think of the Why's.

Mobile Installation Testing – Step 1

Today, more and more people install applications on a smart phone as companies push their mobile strategy forward to go mobile in addition to desktop, or just go mobile, period. When we work with our clients for mobile testing projects, one of the first steps is trying to install these applications. We almost always run into similar problems across applications, so I thought I’d share some of these points.

Implementing Agile – Getting The Right Team

For implementing agile development methodologies, not only do many talk cross-cultural teams, but with respect to agile, many discussions arise regarding cross-functional teams and the user of specialists versus generalists. The problem with generalists is that although they may understand a problem, they don’t have a deep enough understanding to solve the problem. While some propose have a combination on the team, others strongly favor one or the other.

Software Test Team Management – Collaboration and Communication in Daily Activities

As a project manager in XBOSoft, I focus on satisfying our clients which is dependent on how well I manage our testing team. Test team management requires that I communicate with team members frequently every day. In order to be able to function as an efficient team, I try my best to develop effective team communication. The five most common and effective ways we use to communicate are: 1. Team meetings 2. Email 3. IM tools 4. Team collaboration tools 5. Face to face/1-1 talks Team Meetings: Meeting in a conference room with team members directly can deliver information to all members at the same time, and it also helps to collect different ideas from different team members.

Software Quality Metrics – Top Reasons for Failure

Have you implemented a software quality metrics program? If so, then you know its not easy and that metrics programs often fail. Why? Software Quality Metrics - Top Reasons for Failure --Metrics don’t measure the right thing --Metric becomes the goal --Metrics don’t have consistent context so they are unreliable --Measurements used are not consistent --Metrics don’t answer the questions you had to begin with --Metrics have no audience --Measurements are too hard to get --Metrics have no indicators so cannot evaluate

Software Test Plan Checklist

Our clients often ask “How and when the real software testing activities can be started?”. My answer has always been the same: “Once the Software Test Plan is DONE and it gets approved by you!” The Software Test Plan is one of the most important documents for a test project and is usually the first deliverable to our clients. Only after the test plan is approved will our Testing team start real testing activities. From my experience, a Software Test Plan should contain the following information at minimum: Test Scope Documentation Test Methodology Schedule Test Entry/Exit Criteria Test Tools

JSAS Test Automation

More and more companies are now using Agile as their development methodology. This requires that test cases be executed, completed in a short time, and repeated very often. To reach these objectives, automated testing is a must.

There are many ways to setup your automation testing system. The purpose of this blog is not to compare andconclude which one is the best; but mainly to show an example of creating and executing JSAS test automation, one of the automation platforms that we’ve been using lately. .

First, what’s “JSAS”?

Testing Securities Exchange Systems – Tips

Testing Securities Exchange Systems is very complex and requires a significant amount of domain knowledge. Many of the domain-related rules are related boundary values and the change of some values evokes other changes as well. Here are a few examples of where we always ensure adequate test case coverage to handle these situations:

Agile Testing with Jared Richardson and Philip Lew – Webinar March 20 2013

We are happy to announce that March 20 at 10 AM EST we are holding an agile testing webinar with two veterans in the field: Jared Richardson and Philip Lew. Jared and Phil will discuss the changes needed for QA and Testing when working in an agile environment. Agile Testing Topics covered include: - Agile development trends - How to test 'agile' - How to implement scrum - Typical scrum testing bottlenecks and how to solve them - Testing agile requirements - Agile test metrics For Jared Richardson & Philip Lew Jared Richardson Jared is a software consultant. [...]

Reduce the Time Spent on Testing – Testing Strategies

Reducing time on testing is all about effectiveness, not only for the testing process, but the entire development process. The further upstream that defects are found and eliminated, that means less defects found in testing or less defects to be found in testing. Therefore, by deduction, less time spent in testing. In terms of finding defects further upstream, most organizations don’t think of the term ‘defects’ until there is a final product to find fault in, but the term defect can be used for any mistake in the process that would lead to a defect in the end product. This means

Gray Box Testing

More and more, testing requires higher-level testers that can not only tell developers ‘this is incorrect or broken’, but also analyze where and why it happened. Gray box testing provides a deeper level of testing that can provide this information so that the developer can pinpoint the defect’s cause more readily. It’s a combination of white and black box testing where the tester partially knows the internal structure of the software and can develop test cases that apply to the inner workings of the software. Different from white box where the internals of the product are tested in detail but not necessarily from an end user viewpoint, gray box approaches the product from the user viewpoint as in black box testing, but with knowledge of how the underlying components operate. In this way, different types of test cases can be written which dig deeper into the software but from the end user point of view.

Agile Testing – Using an Agile Methodology Mindset

I've been doing lots of reading as well as talking to many people about the whole agile development movement and where it's going. What I've discovered is that there is no agile method that is right and to be 'agile' requires being agile about going agile, if that makes sense. Here are a few items as food for thought that I've picked up in the last few weeks: 1. Agile is an interaction model; it's about collaboration, not just sticking to the 'plan', but

Improve Software Quality Beyond Dev and Test-Quality Process Assessment Webinar

Improve Software Quality - Find Out How In This Webinar October 25 2012 - We held a webinar on Quality Process Assessment (QPA), our software quality improvement service that takes into account how to improve software quality from the viewpoint of the entire life cycle of your software product including phases that are often overlooked such as sales, marketing, customer service. Software quality is not a spice you add at the end. It must be baked in from the beginning! Enjoy the recording! Jan

Quality Process Assessment – How to Improve Software Quality – Webinar Announcement

October 25 at 10 AM EST we are holding a webinar in which we explain how XBOSoft’s Quality Process Assessment (QPA) can help you prevent defects throughout your software products’ entire life cycle, above and beyond development and testing. We show how to examine your software product's lifecycle and how each phase impacts your customers' view of the product's quality. This includes phases such as: - Sales & Marketing-Product/Project Sponsor (intra-Company software) - Product Management (Requirements) - Development - Quality Assurance - Customer Service/Tech Support In this webinar consultants from XBOSoft will share with you their first-hand experience. You'll learn: - [...]

Android Mobile Testing – XBOSoft Mobile Testing Webinar

Wednesday, September 26, 2012 11:00 AM - 12:00 PM EDT we have another webinar on mobile testing. This time, our focus will be on Android Mobile Testing. Two mobile QA veterans (yes they exist) will discuss testing strategies to best cope with Android Device Proliferation. They will answer the question: How to maximize your testing coverage while minimizing your testing efforts. During the webinar you will learn: Effective and efficient mobile testing strategies to counter the specific issues related to Android About the concept of a device family, where a few devices in a family will give a large percentage [...]

Regression Testing – Risk Management and Test Case Prioritization

We often have conversations with our clients about risk management and regression testing because these days with development cycles so short, we rarely have time for full regression. So we have to choose wisely where to spend our time. Manual testing, automated testing, exploratory testing, platform compatibility, etc. It's not an easy task in developing a test strategy in terms of where to put our effort

Defect Writing Best Practice Guidelines

Defect reporting is one of the most important QA activities in software testing. Sure, we devise test strategies and plans, and test cases, but defects are the main ‘product’ that we produce that people can see as the result of our work. But what constitutes a ‘good’ defect? What are these elements’ definitions? I’ve been working in QA for 7 years now, so I thought I’d share some of our best practices: Summary/Subject/Title A short sentence to describe the issue: What is the issue? Where does it happen? Don’t put too many words here since many Defect Tracking Systems (DTS) usually have a text length limitation. Example: Error occurs after clicking "Load" button in home page.

Test Management – Assembling a Test Team

Last time I wrote about interviewing testers and assessing their LoadRunner skills. When assembling a team, you may need testers with LoadRunner skills, but you also need to have a balanced team. Putting together a test team effectively depends on the type of project and skills required, but in general, we like to have a blend of people. When we put together a team, we think of balancing not only skills but personality traits:

Financial Software Testing – Best Practices

We’ve been working with a financial application that does account reconciliation for several years now. The financial software we test conforms to SAS70 (Statement on Auditing Standards No. 70), so all of the data and workflows are designed according SAS70. Although we aren’t accountants, certainly testing this type of software needs a more careful eye than ordinary UI testing, so I thought I’d share some of the best practices developed by our team over the last few years.

Healthcare Software Testing Strategies for HIPAA Compliance

When testing healthcare applications, there are many government regulations that the tester must be aware of. These regulations are automatically a part of any requirements, even if not explicitly stated. These regulations will be the same for all healthcare applications so it is incumbent for any testing organization to not only thoroughly understand these regulations, but also ensure that the test strategy and test plan accommodates them. For the health care industry in the United States, the main law for these regulations is HIPAA.

Software Quality Metrics for Quality in Use

When most people think about software quality metrics, they think about defect related metrics such as: Total defects, Defects at delivery, Mean time to defect, Defect burn rate, Mean time to failure, Mean time between failures, etc. While examining defects is a start to developing quality metrics, it’s just a start.

Test Process Improvement (TPI) – Benefits versus Costs

Nowadays, many companies consider integrating TPI into their testing processes. However the questions of how much does a TPI effort cost and will these costs exceed its benefits have been raised by many practitioners. This article discusses and elaborates TPI’s benefits and costs, so that you can decide whether TPI is justified. Most of the time, a TPI effort is triggered by one for more of the following three testing issues: Testing takes too long Testing is too expensive False expectation between developers and testers The primary goal for TPI is to improve the product’s quality through making the testing [...]

Using Esxi to setup test environments quickly and easily

In most testing projects, we need to setup and manage many test environments - from Windows 2000 Advanced Server to Windows Server 2008 R2, from Redhat Enterprise 5 to Solaris 11, from Microsoft SQL Server 2005 to Oracle 11g R2. This is required because testers frequently switch among them to verify and validate the quality of the products across multiple platforms. We’ve found that setting up and managing many test configurations can be accomplished well with VMWARE Esxi. VMWare Esxi, now renamed as "VMware vSphere Hypervisor", is a popular virtualization solution and has many benefits:

Software Quality – Finding Defects Early – Requirements Defects

One view on software quality is the absence of defects. Of course, how do you know if all the defects have been found? If you can’t find any, does that mean the software is ‘good’ quality? When we talk to our clients about software quality, we try to impress the importance of detecting defects earlier in the development cycle, rather than just testing when development hands over a new build. Research shows and we all know that defects found early are cheaper to fix than those found later, so why not build early defect detection into the process. We all log defects when we are testing the software. That’s what we call ‘software testing’, but what about requirements testing (some may consider this part of software inspection as well)?

Software Quality – What is it?

With the increasing success of cloud deployment and SaaS business models software has replaced many companies. Today’s largest bookseller is not Borders, its Amazon, a software company. Netflix, a software company, left BlockBuster in the dust... As software usage becomes more mission critical in almost every aspect of life, understanding and thus improving software quality also becomes critical. These days, agile methodologies have worked toward integrating QA with development rather than having QA as an afterthought through test driven development combined with... The problem with quality is that it is an abstract concept and cannot be measured easily. It’s presence is difficult to define and see, yet it’s easy to point out its absence. So before finding the solution, whether complex or simple, let’s examine what quality is...

Show Buttons
Hide Buttons