Practical Testing Strategy for Agile TeamJen-Chieh Ko
This document outlines a practical testing strategy for agile teams. It discusses challenges in agile testing and common principles such as shared responsibility and continuous testing. It recommends treating test automation as software development, with an agile mindset focused on value. The strategy suggests starting automation early to provide feedback, and following practices like code review. It provides tips for different testing activities like static testing, unit testing and performance testing. The overall message is that agile testing requires handling high value parts first, early and frequent testing, and for testing activities to work together continuously with a common strategy.
The document summarizes the results of an exploratory testing survey with 78 responses. Key findings include:
- Most respondents have 3-5 years of testing experience and work primarily on applications with a graphical user interface.
- Common testing activities included integration, system, and regression testing. Mind mapping and Excel were commonly used for tracking.
- Respondents felt exploratory testing is more interesting, flexible, and finds more issues than scripted testing. The main challenges are lack of structure and documentation.
Design sprint experience at Trend MicroJen-Chieh Ko
This document summarizes Trend Micro's experience with design sprints for internal training and innovation projects. It discusses several design sprints they conducted in 2018-2019 for their employee training program and business administration and Deep Security teams. Lessons learned included needing more evangelism for the approach, focusing on real problems, connecting to company events, ensuring proper logistics and user testing, and validating ideas' feasibility. It also outlines next steps like improving the process based on context and sharing more case studies combining design and development sprints.
Container and Test Automation Management Practices in TrendMicroJen-Chieh Ko
The document discusses containerization and test automation practices at Trend Micro. It describes how the company uses containers, Kubernetes, and related tools to improve their continuous delivery processes. Key practices include using TestRail for test case management and automatically syncing test cases with a robot framework; implementing blue/green deployments in Kubernetes for faster, safer releases; leveraging Kubernetes features like configmaps, secrets, and ingress for configuration management and routing; and monitoring containerized services with Prometheus and Grafana. Testing is also containerized for easier replication of environments and parallel test execution.
This document discusses design sprints and user research. It describes the speaker's experience leading two design sprints within their company to help solve real product problems. They discuss lessons learned, such as allowing more time and ensuring decision makers are present. The document also provides tips for activities within a design sprint like how might we brainstorming and user testing. In summarizing user research tips, it emphasizes understanding user needs and behaviors without influencing responses.
From zero to one - How we evolved our test automation processes and mindset i...Jen-Chieh Ko
The document describes the evolution of test automation processes at Trend Micro for their Deep Security product. It discusses moving from manually managed virtual machine environments to using Ansible for automated and scalable environment setup. It also describes transitioning from the JUnit test framework to the custom-built Deep Security Automation Framework (DSAF) to improve test robustness. Additionally, it outlines the development of various automation tools and dashboards including Lift for installation/upgrade testing, Mothra for consolidated test results, and the use of Elasticsearch, Grafana, and Prometheus for data collection, visualization, and monitoring.
Dale Chang shared his experience working on 3 projects across different countries and cultures using Scrum. The first project failed due to a lack of clear objectives and commitment. The second project succeeded by focusing on competency development and implementing a structured development process. The third project overcame challenges by adapting the Scrum process to better fit the hardware development needs. Throughout the projects, Dale emphasized the importance of having a clear process, building team competencies, and being willing to adapt the process to suit different project needs.