- Agile Testing
- auto insurance software testing
- Automated Software Testing
- Data Verification Testing
- Financial Software Testing
- Game Testing
- Healthcare Software Testing
- Insurance Software Testing
- Localization Testing
- Mobile Performance Testing
- Mobile Testing
- Performance Testing
- QTP Test Automation
- quality metrics
- Regression Testing
- Retail Software Testing
- Security Testing
- Software Test Automation
- Software Testing Metrics
- Test Automation
- Test Case Design
- Test Management
- Test Management and Planning
- Test Process Improvement
- Test Strategy
- Test Tools
- Usability Testing
- User Experience
- Web Application Testing
- Whitebox Testing
- Software Developer & Tester Working Together Agile Style Q&A
- Relationships with end users key to software quality says XBOSoft contest winner
- Tester and Developer Working Together to Achieve Higher Quality Mobile Software
- Software Testing in Boston – XBOSoft at the Better Software Agile Development Conference
- Better Software East – XBOSoft Happy Hour – November 13
Tagsagile agile project management agile testing android testing Automation Testing Coded UI content target data verification defect analysis defect metrics define software quality embedded software testing financial software testing html5 testing L10N learnability localization testing mobile mobile application testing mobile performance testing mobile qa mobile testing pharmacy software testing QA qtp scripting QTP VBS automation quality in use requirements scrum scrum testing software quality software quality measurement software quality metrics Software testing software testing metrics testing testing html5 testing metrics test process improvement test strategy url redirection test url test usability user experience Web Application Testing
Author Archives: Shawn
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: More
One of the main concepts depicted in the Agile Manifesto is close communication among team members. However, in the real world, sometimes we have to face the situation that the whole agile team is split into several sub teams that may not be in the same location or time zone. This situation usually happens with global companies or when some work is outsourced to a services provider that may be in another country. As a specialized software testing company, we often have the situation where our customer develops their software while depending on us to be responsible for the quality assurance as a remote agile testing team.
With agile development methods now becoming more popular, we have had to adapt from a waterfall situation where we wait for a software build based on fixed time periods to a‘remote agile testing’model. To do this, we must have a very good plan. But even before starting the project, we think about a few soft factors that have a significant impact on success but are often forgotten. These include: More
This blog shortly introduces a new plug-in tool for Coded UI. Coded UI is the automation testing tool which is included in Visio Studio 2010 and is becoming more and more popular. Coded UI has many advantages such as the integration with TFS (Team Foundation Server) and the support of Silverlight. However, there are still some limitations compared to other more mature test automation tools. One of the biggest issues is that in Coded UI, the code for defining objects is mixed in with the automation scripts which cause difficulties when it comes to maintenance.
Recently, I found a new plug-in for Coded UI, CUITe More
When using the scrum methodology, one of the most important elements is the user story. User stories are the requirement specifications in scrum. Usually, the product owner is responsible for writing and prioritizing the user stories and then explaining them to the team during sprint planning meetings. Sometimes a developer in the team may also help the product owner create user stories to add more technical detail. In many situations, there are no testers involved in the discussion of and creation of a user story. However, it is important for user stories to be written such that they are ‘testable’ in scrum because without accurate and complete testing, the user story cannot be marked as ‘Done’ for the sprint. More
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. More
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: More
Currently, more and more small to medium size development projects choose using Scrum because of its simplicity and effectiveness. On the other hand, it may be a challenge for testers who may be used to working with in a traditional development model to adapt to the activities in a Scrum team. For testers, there are many differences between Scrum and a traditional process: More
With Microsoft’s Visual Studio having an integrated development and test environment, we’ve been working with several customers using Coded UI for test automation. Coded UI is a new capability of Visual Studio 2010 which provides a way to create fully automated tests to validate the functionality and behavior of your application’s user interface.
The following are some benefits from using Coded UI:
Support for Microsoft technologies (e.g. Dot net): With the application developed by Microsoft technology, the objects contained in the application can be easily recognized by Coded UI and the properties of objects are visible.
Friendly UI for automation testers to create scripts: Not only because it is based on C# and Visual Studio IDE, but also it delivers an additional GUI to help testers modify the existing scripts (this feature is in service pack 2).
Easily integrated into TFS server and controlled by Test Manager. By using Test Manager, testers can decide when the automation scripts to be executed and which machine (physical/virtual) to execute them on. The automation scripts will be executed automatically based on the schedule and then the results will be reported.
However there are some limitations in Coded UI. For example, it does not support Flash and Flex technology and currently only supports IE and Firefox browsers.
Based on my experience, I’ve listed out 5 tips in implementing Coded UI for test automation to help you save some time and get on the fast track… More