MORE DETAILS ABOUT TOPICS
Software Testing Trends | Paul Holland
- Trends in Software Testing: There has been a slow realization among the top executives that simply outsourcing testing to the lowest bidder is not resulting in a sufficient level of quality in their software products. In this session, Paul Holland will discuss how American companies are starting to reconsider “factory school” testing and are no longer satisfied with the current situation of simply outsourcing their “checking”. As the development side of software continues its dramatic shift toward Agile development – what role can testers have and how can testers still add value?
Fault Localization: Where May Be The Root Cause Of A Bug? | Tho Quan
- To debug, programmers must first be able to identify exactly where the bugs are, which is known as fault localization. Basically, this approach aims at prioritizing the program code based on its suspicious levels. Thus, it allows the code segments which are more likely to contain bug to be examined first. In this talk, we present the fundamental techniques of fault localization, which include model-based, proof-based and spectrum-based techniques. In addition, we also give a demonstration of a self-developed online education tool to help students locate the potential root causes of the programming errors occurring in their exercises.
Bad Metrics and What You can Do About It | Paul Holland
- Software testing metrics are used extensively by many organizations to determine the status of their projects and whether or not their products are ready to ship. Unfortunately most, if not all, of the metrics being used are so flawed that they are not only useless but are possibly dangerous—misleading decision makers, inadvertently encouraging unwanted behavior, or providing overly simplistic summaries out of context. Paul Holland identifies four characteristics that will enable you to recognize the bad metrics in your organization. Despite showing how the majority of metrics used today are “bad”, all is not lost as Paul shows the collection of information he has developed that is more effective. Learn how to create a status report that provides details sought after by upper management while avoiding the problems that bad metrics cause.
Value-based software testing, An Approach to Prioritizing Tests| Vu Nguyen
- As a software tester, you may often face a situation in which your customer requires completing testing faster than you can handle given your effort and the amount of test. For example, in order to complete testing 2000 test cases for a build, you need at least 10 days to complete all testing. However, your customer needs to test and release the build within 5 days. You need to make a tough decision to handle this request. This presentation offers you one of the approaches that you can pursue. The presentation discusses an approach to prioritizing test cases using the principles of value-based software engineering. The approach is based on the principle that not every test case is equally importantly, e.g., not each of the 2000 test cases has the same value. A simple Excel tool will also be provided to allow you quickly prioritize test cases and select the ones that generate best value for your customer.
The Psychology in Software Testing | Hoang Nguyen
- This presentation will examine the psychology of the software testers carrying out the testing will have an impact on the testing process. It shows that software development and software testing both aim at meeting the predefined requirements and purpose; both are highly creative jobs but the general outlook towards two individuals is psychological rather than different classification. A software tester requires not only technical skills similar to the software development, but also needs to acquire other personal skills and characteristics with respect working environment, emotions, visualization, belief, critical thinking, etc. The quality of the testing job done by the software tester is directly proportional to his or her psychological maturity and background acquired, adopted and developed with experience, age, and personality traits.
Software Testers: From Good to Great | Mush Honda
- Typical software testers focus on learning ‘Hard’ skills associated with the responsibilities of their role. However, these skills allow them to become a "Dependable" or "Knowledgeable" tester, rather than a "Great" tester. What are the skills necessary to take you to the next level within your ladder of testing career, to become someone known as "Great" tester? This presentation will identify some of the key skills that can take you to the next level and provides an easy-to-follow roadmap on mastering those skills.
Deadly Traps of Test Automation | Thao Vo
- Test Automation significantly contributes advantages and benefits to software testing success. However, test automation projects, to some extent, have been not succeeded as stakeholders' expectation. This topic aims to suggest solutions for the following problems to prevent from automated testing mistakes.
Apply Automation once Executing Ad-hoc Testing | Hoa Le
- Typically, different software testing methods and techniques are applied to fully test a project. Ad-hoc testing, which is characterized as testing with no explicit planning, test designs, or documented test cases, is one of the most widely-used methods in agile projects. Automation testing uses software tools to perform or support test activities such as management, test design, test execution and results checking. Automation testing can be effectively applied to repetitive necessary tasks in a formalized testing process or other tests that are difficult to execute manually. This presentation introduces a strategy by combining these testing approaches to improve the effectiveness of software testing.
Test Estimation in Practice | Vu Nguyen
- Software testing is an essential activity of the software development lifecycle. To ensure quality, applicability, and usefulness of a product, development teams must spend considerable time and resources testing, which makes the estimation of the software testing effort, a critical activity. This presentation presents a simple and useful method called qEstimation to estimate the size and effort of the software testing activities. The method measures the size of the test case in terms of test case points based on its checkpoints, preconditions and test data, as well as the type of testing. The testing effort is then computed using the size estimated in test case points. All calculations are embedded in a simple Excel tool, allowing estimators easily to estimate testing effort by providing test cases and their complexity.
Behavior-driven development (BDD) and automation testing with Cucumber | Thong Nguyen & Trong Bui
- “How are business users assured that all features are built and tested?”. “Test cases written by the test teams are too technical for business users”. If you find yourself in the above situations, Behavior-Driven Development (BDD) may be a good choice for your team. In this presentation, we will discuss BDD as an agile development practice, automation testing using Cucumber as well as the advantages and disadvantages of BDD/Cucumber.
Metrics and reports from QA | Mush Honda
- As a part of testing management in a project, test leads are often requested to provide reports and measurements of progress being made by their team. Most of them limit their reports to templates found on the Internet or by simply providing number crunching metrics requested by the project stakeholders. The intent of this presentation is to highlight key goals and reasons and for collecting and reporting information from a tester’s perspective. Attend this presentation to understand the purpose of metrics and how to establish test-centric metrics and to learn a typical metric lifecycle that will enable to you provide insightful progress of your activities in the right context of the project.
Automated testing on mobile devices for iOS and Android | Binh Nguyen
- Mobile application testing on iOS or Android can be quite a challenge for a Quality Assurance team. One reason is that mobile applications are often required to function on a variety of devices featuring different hardware capabilities, configurations, and specifications. Many different types of testing including automation are required to cover different areas of the application. Many people believe that automated testing may replace manual testing almost entirely. In reality, however, automated testing is still not able to cover all the types of testing that manual testing does. Automation Mobile Testing: framework, tools, some suggested solutions.
Best practices in performance testing | Quang Nguyen
- Performance testing is an essential component of software testing to ensure quality of many software applications. Failure to test software performance may result in serious problems when the software is deployed. This presentation discusses the best practices that can be applied for performance testing. This presentation also provides a method that helps you go through all key steps to perform performance testing successfully.