RSS
Categories
- Agile Testing
- Automated Software Testing
- Data Verification Testing
- Financial Software Testing
- Game Testing
- Healthcare
- Healthcare Software Testing
- Insurance Software Testing
- LoadRunner
- 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
-
Recent Posts
Recent Comments
- Kranti on Data Verification Testing
- shivakumar on Using XPath Axes to Locate Elements in Selenium Webdriver
- Rendezvous Software Performance Testing with Loadrunner | XBOSoft Software Quality Blog on Testing Retail Software – Ecommerce Testing Considerations
- Kristin on Coded UI Test Automation – CUITe Plug-In
- Santosh on Software Testing Trends – Software Industry Trends
Tags
agile agile project management agile testing android testing Automation Automation Testing Coded UI content target data verification Defect defect analysis defect metrics define software quality financial software testing L10N learnability localization testing mobile mobile application testing mobile performance testing mobile qa pharmacy software testing QA qtp scripting QTP VBS automation quality in use requirements scrum scrum testing Silktest software quality software quality measurement software quality metrics Software testing software testing metrics testing testing metrics test process improvement test strategy url redirection test url test usability user experience Visual Studio Web Application TestingLogin
RSS
Author Archives: Shawn
Remote Agile Testing – Tips For Success
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
Posted in Agile Testing, Test Management
Tagged agile testing, communication, remote agile testing, remote testing
Leave a comment
Coded UI Test Automation – CUITe Plug-In
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
Posted in Test Automation
Tagged Automation Coded UI, Coded UI, coded ui test automation, codedui
1 Comment
Scrum Testing Best Practices – Writing Scrum User Stories
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 – 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. More
Testing Insurance Software – Tips and Lessons Learned
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
Adapting to Agile-Scrum Testing
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
Five Tips in Using Visual Studio Coded UI
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