Quality is Key at SofTec Asia Conference

At the beginning of August, Our CEO Philip Lew spoke at the Softec Asia 2017 conference in Kuala Lumpar, Malaysia. With the theme "Testing As A Service," speakers tackled the topic with knowledge in all aspects of improving software quality. Here is a visual look at what some of the speakers focused on in their presentations.

Softec Asia 2017 theme Testing as a Service.

API Testing Issues

When conducting (application program interface) API Testing, let’s first consider what an API is, code that enables two software programs to communicate with each other. The API defines the parameters and methods that a developer can request services from an operating system (OS) or other application and typically consists of calls with a required syntax consisting of a predefined set of nouns and verbs. Simply put, APIs enable applications written in different languages and for different platforms to communicate with each other. Usually, APIs are provided for third-parties via a software development kit (SDK) or published openly on the Internet. Some of the issues in using APIs and therefore API testing include:

Cross Browser Testing – Quick Tips

Today there are many browsers used on both on desktop and mobile devices. Some users utilize the default browsers pre-installed on devices while others install 3rd party browsers such as Opera. Ensuring website compatibility with most popular browsers can sometimes be a challenge for developers. If a developer wants to ensure browser compatibility across devices, then cross browser testing is a must. Some of the aspects in testing across browsers include:

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”?

Performance Testing and Test Automation Best Practices Webinar

On August 8 2012, together with BlackLine Systems, we held a webinar on Performance Testing and Test Automation Best Practices entitled: How to Achieve and Maintain High Quality SaaS Software in the Cloud Donna McCollum from Blackline Systems and Philip Lew from XBOSoft discussed lessons learned and best practices on how to set up test automation and performance testing for cloud software that is delivered with a SaaS model. If you'd like to keep updated on upcoming webinars on performance testing or test automation or other QA related topics please follow us on twitter: Follow @XBOSoft

Software Quality Metrics and Evaluation – QUATIC 2012 Conference Presentation

Some of the research that we've been doing on web application quality, quality evaluation, and software quality metrics, has been chosen for presentation at the Quality in Web and Mobile Engineering Track. The title of the paper I'll be presenting is: Using Web Quality Models and Questionnaires for Web Applications Understanding and Evaluation. Fortunately, our research was also selected as one of the best papers of the conference. So, I'm so lucky... I get to present the paper in the conference main track as well! So if you have a chance to come see me in Lisbon on Sept 3-4, 2012, I'll take you out for dinner! Software quality and User Experience In summary, the paper presents

Web Application Testing – Security and Performance Inspection using Fiddler

Fiddler is a Web Debugging Proxy tool which logs all HTTP(S) traffic between your computer and the Internet. Fiddler allows you to inspect traffic and can be used by developers to debug web programs. It can also help testers inspect and examine the traffic between the user side of a web application and web server. I’ll just talk about the tool from a tester perspective, and discuss some simple uses that we’ve run across.

How to Test URL Redirection

How toTest URL Redirection Website URL redirection is used in several instances. For example: • When the domain is reallocated from www.example.com to www.anotherexample.com. Because people will still keep www.example.com, instead of the new one for the website in their bookmark. • When the webpage is renamed or reallocated. • When you expect different content for different locations of your user population. An airline website for instance; the default “from” location for a ticket would be Chicago if the user IP is from Chicago, etc. Testing redirection in a live environment is simple. Just type in the domain alias in the address bar, and then check the final response. But what about the test environment?

Show Buttons
Hide Buttons