Cloud communications software provider Mitel benefits from testing expertise

Cloud communications software provider Mitel was experiencing various difficulties with new software releases due to lack of sufficient testers on staff. XBOSoft was hired to provide the needed manpower. Over time, XBOSoft's range of services has expanded, with ever greater satisfaction on the part of the customer.

Test Case Development – Test Like a Robot

There were still a few remaining questions from our webinar with Srilu Pinjala in July on Test Case Development - So You Think You Can Write A Test Case that we wanted to address. It was Srilu's opinion that test cases should be very detailed and document the functionality of the software. Her view was that this way test cases can then be used by anyone and at a later date. She coined the phrase Test Like a Robot which I found interesting. Should one really want to be like a robot?

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). . .

Agile Test Cases – Test Case Development

From our webinar with Srilu on "You think you know how to write a test case", we had several questions. With regard to agile test cases , "What do you do in the mean time between development and when the app/software is ready? Is it not advisable to write the test cases based on the product specification instead of waiting for the software to be ready?

I had a chat with Srilu about this, and here is what she says. . .

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.

User Acceptance Testing – Measuring Test Coverage

During our agile webinar, we had many questions we couldn't get to. Here's another one on User Acceptance Testing

Question: Assume an UAT (User Acceptance Team) where they do not have separate user story/functional requirement as such. Functional points are designed in such a way that delivery is done in modules. Groups of modules that deliver functions will be tested by UAT. In this case, how can we measure test coverage %?

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:

10 Ways to Reduce the Cost of Software Testing-Agile Testing

As organizations move toward agile, they find that testing is not just at the end anymore. Rather, it’s all throughout the development cycle. But then the question is, well if testing is throughout the entire cycle, will it be more expensive than just testing at the end? But this premise is faulty because testing at the end leads to problems or defects found at the end, which in turn can be very costly. Not to mention downstream costs if critical defects reach production. Given that, we've come up with a list of some of the ways that we work with our clients to either reduce the testing effort and/or make the testing effort more focused and productive/efficient.

GIS Software Testing – Lessons Learned

With the rapid development of information technology, Geographic Information System (GIS) have been widely applied to almost all domains where geographic coordinates (or location) add information and value to the end user. The most common, started with Google maps where they recently have enabled even bicycle routes in beta. Almost all mobile apps where there is a location involved include a mapping or GIS function and these functions continue to become more and more integrated into the heart of the app. Additionally, the complexity of GIS software has continued to increase which has put pressure on software quality and reliability. Compared with testing other types of software applications, GIS software testing has its own particular characteristics. Some of these considerations include:

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.

Testing Insurance Software – XML Data Verification – The Core of Insurance Software

Testing insurance software can be divided into front, middle and back office. When we examine the front office, we pay attention to the UI part. However, the front office is just a small part of the whole system. There are other components that need to communicate with the front office. XML is one of the predominant data formats used for this communication.

Testing Retail Software – Ecommerce Testing Considerations

As part of our ecommerce software testing practice, we have been testing several retail websites in past several years. The main purpose of a retail online business is to attract customers and then basically get them to buy your products. So the main objectives are to show product details to potential customers, and make it easy as possible for them to find the right product and then of course pay for it. I’ll just discuss the first part since the payment process is a whole document in itself when it comes to testing. A successful retail website entices users to be more interested in the product and leads them to want to learn more about the product details, either in graphics or text. The most important factor is to organize and show such information to keep the customer moving forward toward your objective; buy. Given this, based on our testing experience, we need to prioritize our testing effort based on the special objectives of retail ecommerce:

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

Show Buttons
Hide Buttons