Retail and Ecommerce: Digital Transformation and What It Means For Software QA Digital transformation is a big idea and means many things; one industry that has been most affected is retail. Many consumers prefer to shop online instead of visiting retail storefronts. Gone are the days when shopping entailed going to the mall to check out different stores, compare products, finalize the purchases and go home with an armful of shopping bags. While the customer journey continues to get easier, it also continues to grow in complexity. To succeed, online retailers will have to shift focus from pure retailing [...]
Adaptability to a changing environment is the key to survival, so said my father. More recently, brick and mortar has come under siege from the online retailers, What is dramatically different about today, is these online retailers are not really retailers, they are software companies, focused on retail. The backbone of today’s retail business model is ...
This blog discusses some of the issues in testing accounting software and in particular when validating and verifying International Financial Reporting Standards (IFRS), set by the International Accounting Standards Board (IASB). In a nutshell, IFRS is concerned with the preparation of financial statements. While GAAP ensures ....
Ecommerce testing is the best way to keep your retail software run as smooth as possible and attract more customers, helping you to grow your business. Find out what it takes to do ecommerce testing and what is the best approach.
As an accountant, CPA, and Quality Assurance Analyst, Jan Lundeen has done, reviewed, and tested many reconciliations during her career. She shares a few real-life examples from an accountant's point of view on account reconciliation and financial software testing.
It’s a long plane ride to Kuala Lumpur, Malaysia. That’s where SofTec Asia 2017 was held the first few days of August. But, with all that I learned — both through formal presentations and informal discussions with fellow presenters — it was well worth the trip.
The 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.
Without a vocal advocate — and managers willing to stand up in support of it — company culture won’t change, and users’ needs are going to go unmet. And if there’s no strong advocate for testing within the company, the results can be disastrous — and not just in the marketplace.
“Since we began working with XBOSoft as our quality-assurance partner five years ago, our entire process of developing and releasing new software has become much smoother and more efficient,” Mobile MedSoft CEO Duke Yetter said.
Release Pace of New Healthcare Software Propels New Strategies for Quality Assurance/Testing
Software Should be Made for Humans
I attended Cornell Silicon Valley 2017, #CSV17, in early March. I’m a graduate of Cornell, and have found all of the Cornell events I have attended beneficial. This year’s conference was no exception. It featured presentations on various types of software innovation, some designed to plumb our humanity, others designed to replace it. The event never fails to rejuvenate me, inspiring new ideas and fresh thinking.
I listened closely to the keynote speech on reverse-engineering the brain for intelligent machines and thought the most important takeaway was that current algorithms are very fragile, not adaptive. Yes, we have gone beyond the first stage of artificial intelligence. But for truly adaptive and learning algorithms, we have a long road ahead. Applying this to our field of software engineering and, in particular, software quality and testing, I get a clearer picture of what’s ahead for software testing. We will see test cases that adapt and change, applying testing algorithms rather than specific test cases. Just as there will be software innovations in development, they will occur in quality assurance as well.
Yes, we have gone beyond the first stage of artificial intelligence. But for truly adaptive and learning algorithms, we have a long road ahead.
A new age is upon us: the Mobile IoT Period. Driven by the proliferation of mobile devices, and in particular the smartphone, we now face a complex and integrated infrastructure of technologies and concepts called the Internet of Things (IoT), all connected by mobile technology. The challenges we face to ensuring software quality for the myriad technologies that are being shaped by the Mobile IoT Period are daunting. Let’s take a look at the Top 7 Challenges in the Mobile IoT Period. Big Data Big data would not be possible without mobile network technologies to get the data from one [...]
San Francisco, CA (PRWEB) February 8, 2017
The changes sweeping through the healthcare data landscape created substantial challenges for the makers and users of healthcare software. Healthcare IT departments have often struggled to keep up with demands from healthcare providers, patients and government regulators. That’s why software developer Mobile MedSoft has partnered over time with XBOSoft to manage its quality assurance: XBOSoft consistently delivers high quality services and ensures that, when Mobile MedSoft releases a new product, it performs as expected.
Five years ago, Mobile MedSoft turned to XBOSoft to manage its healthcare software quality control. Since the partnership formed, the two companies have developed a deep and highly effective relationship that, says Mobile MedSoft President and CEO Duke Yetter, has resulted in better end products for the company’s long-term care pharmacy customers.
San Francisco, CA (PRWEB) February 8, 2017
XBOSoft will mark its Tenth Anniversary at the DeveloperWeek trade show in San Francisco. Founder and CEO Philip Lew and marketing vice president Steve Gorhes will be at booth 241 for two full days (Feb. 14-15) during the run of the show, Feb. 11-16.
The company celebrated the milestone in January with XBOSoft’s employees in Beijing, China, who perform most of the software testing and software QA consulting.
Testing Multi Currency Applications Means More Than Arithmetic Testing multi currency applications is difficult because it permeates the entire application. Once multi-currency settings are applied, it will penetrate all of the data and how it is processed. It is like adding salt while cooking, it is impossible to get the salt out. Even worse, you can’t just add more food or water to dilute the salty flavor. As such, for most applications supporting multi-currency, the multi-currency setting switch usually cannot be turned off once it is activated. When testing multi currency software, you'll also understand when and what currency should be used in order to thoroughly understand the business viewpoint when designing your tests. This impacts how
We came, we saw, but we didn't quite conquer. XBOSoft had a wonderful time at the European Software Testing awards this year- and were very proud to have been nominated as one of the Finalists for the Best Overall Testing Project - Finance. Barclays Bank pipped us to the post - congratulations to them!
We're getting ready for tonight's European Software Testing Awards 2014 as we've been invited as Finalists for the Best Overall Testing Project – Finance. Let's see if our case study in providing manual regression testing with Agile Scrum workflow in Financial Accountancy space wins the category! To win the award we had to show evidence of commitment to high quality and standards, as well as effective utilisation of best practice methods and evidence of delivering projects on time and within budget. The software testing awards will be the first we've submitted in Europe, so wish us luck!
We're about to take part in the AHCA Expo convention this week in Washington DC - showcasing our extensive range of software testing services in the healthcare market - come visit us at booth #426 if you are in the area. By visiting us you qualify to take the Quality Stars Software Challenge and win an iPad Air! Are you attending the AHCA or Leading Age conference this month? If so you can enter our Quality Stars competition to win an iPad Air! We’re looking for software with the least amount of defects to be crowned our Quality Star [...]
Compared with other insurance products, testing auto insurance software is simple and direct. There are not too many complicated rules. However, auto insurance software testing is very important since most insurance companies sell auto insurance in their product portfolio. Therefore, understanding the rules and important testing points are critical for the testing team. For most of auto insurance products, there are 4 main sections: personal and contract information, car information, insurance coverage and calculation. For testing auto insurance software, we’ve compiled a list of important business rules and check points:
Testing XBRL, the financial reporting standard, requires domain knowledge in order to understand how to develop an effective test strategy. When we test XBRL, we need to first understand it’s specifications, taxonomy and instance documents: XBRL Specifications This defines specialized terms, indicates how to create financial reports based on XBRL Specifications, and how to create XBRL Instance Documents and XBRL Taxonomy.
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:
We test accounting and financial software on a daily basis. Probably the most prominent thing we have to keep in mind when testing are the business rules. With accounting software designed to service US-based companies, they must adhere to GAAP, while International Financial Reporting Standards (IFRS) have had effect mostly for international M&A and international subsidiary transactions. However, in May 2011, the SEC published a paper incorporating IFRS into US GAAP with a migration plan. So many public companies and hence the accounting and reconciliation software that they use will soon have to incorporate these changes. One of many elements includes revenue recognition. Differences require a detailed, transaction-based analysis and therefore an understanding of business rules in the way companies operate and provide services.
Games these days have increasingly complex interaction schemes. Great for the gamer! But this also leads to many quality related issues in order to optimize the gamer’s experience.Some of the issues that are particular to game testing include: Usability: Probably one of the most important aspects is
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.
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:
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 so that we can minimize risk while achieving the level of confidence that we want that the release is ‘defect-free’.
As part of our healthcare software testing practice, we have been working on a medication dispensing system. Medication Dispensing software, part of a Medication Management system, allows pharmacy inventory to be managed from its arrival in the pharmacy to dispensed medications, implementing multiple bar code checks for accuracy. It works throughout the facility and sometimes crosses multiple hospitals. Using this type of application, technicians can quickly and securely pick from the carousel and other devices. Monitoring and dispensing medications is highly regulated and requires a complex and highly secure system. Business rules and features are quite complex, so testers need to prioritize the features and priorities. In our testing experience, we found the following top 4 items to prioritize our testing efforts.
Insurance is a broad industry covering health, personal property, liability, automobiles, mortgages and more. With such a wide range, some companies specialize while others offer comprehensive product offerings. In the last year and a half, XBOSoft has worked together with another software company that mainly focuses on developing software for the insurance industry. During this time, we’ve accumulated knowledge in insurance software and have gathered some key points that we think are important for testing insurance software:
May 31 we held a webinar with Duke Yetter, the CEO of Mobile Medsoft and our own Phil Lew, in which they discussed setting up the right usability and UX measurements for testing mobile healthcare applications. It was a very interesting talk where Duke shared his ideas and experiences from the perspective of a health care executive and Phil shared insights based on years of experience as a consultant and his academic research. Please see the video below: If you are interested in usability more resources can be found here.
If your users cannot figure out your application in less than 30 seconds they’re gone. The UX and usability of your applications are their competitive advantage. May 31 11:00 AM Eastern UX and Usability Expert Phil Lew will discuss how to set up and implement the right measurements to continuously deliver the applications your users love to use. Together with RNA Health Phil will present a case study for a mobile health care application. See you there!
A Data Warehouse (DW) stores data where it can be analyzed, archived, and secured. DW products are used to manage large amounts of data (now recently called Big Data) and make it easy for users to make business decisions. With mobile devices, social networks, and web-based software collecting so much data, many organizations are beginning to sell not only the data itself, but analyzed or scrubbed and filtered in some way. We’ve recently worked on testing some data warehouse projects and wanted to share a few quick QA tips specific to this domain...
We have been testing a pharmacy management software system for years and wanted to share a few notes from our testing experience during that time.
We’ve been testing healthcare software for several years and in particular, pharmacy management software. Testing healthcare software products definitely requires a different angle, so I thought I’d share some of our expertise and experience. Roles and workflows. Physicians, pharmacists, nurses, and technicians all have different permissions and use the application differently so the test strategy and test cases must specifically account for these peculiarities. For example, a physician is responsible for prescribing an order, while the pharmacist only receives the order. Privileges by role. Each role must be tested for their specific privileges, positive and negative. For instance, only the [...]
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.
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.