Motivation: After starting a new project, the initial planning is done and the very first development activities start. But as we all know, all products are tested, which means at some point (ideally soon after the development activities start) testing activities also start.
So, from the start of the testing till maturity, there is a long and tricky way. In this talk, I discuss what kind of challenges are experienced and how we can cope with them.
I will explain:
* How we managed to collect insights from bugs.
* How we managed releases
* How we reduced testing effort before shipment
* How we maintain the stability of CI/CD.
- Hidden information
- Missing guidance
- Complex and complicated systems under test
- A lot of deployments and limited resource
- Adaptation problems in the team
- Information mining: Walk through and explore the system, Customer Surveys, Requirement Analysis, Specification Benchmarks
- Define processes: Bug Life Cycle, Test Case Life Cycle, Workflows: Code Review Guideline, Acceptance/Exit Criteria
- Decide Tools: Issues, Tasks, Tests, Results, Code
- Maintain Tests: Coverage, Suite Management, Markers
- Automation: Implement the skeleton: Flexible enough for further improvements, Robust and open for RCA, Reporting
- Define Levels and Subsets: Priorities for the executions
Results & Conclusion
In this talk, I will present building a good software testing life cycle and achieving quality in software projects from scratch.
Outline/Structure of the Keynote
- Introduction: Importance of the strategy and the architecture of quality
- Steps of building the quality:
- Continuous learning and ways to reveal information mining
- Define processes
- Test Planning
After this talk:
- Attendees will realize what kind difficulties should be achieved to maintain quality in software projects
- Attendees will see various ways to formulate requirements
- Attendees will see the important aspects of building life cycles for various issues
- Attendees will realize the potential risks of test automation and understand it may be even less efficient than performing manual testing if executed not properly.
Testers, PO, Developers
schedule Submitted 10 months ago
People who liked this proposal, also liked:
Matthew Skelton / Alex Papadimoulis - Matthew Skelton: Interview with Q&A
Mesut Durukal - Common Pitfalls and Life-saving Solutions in Agile TestingMesut DurukalQA Automation EngineerIndeed
schedule 10 months agoSold Out!
Motivation: I have experienced a lot of challenges in both technical and social manners and tried to develop solutions to cope with them throughout all the testing activities that I was involved in. Eventually, I have wrapped them up to make a list of common pitfalls which can be encountered by any tester and some golden rules to successfully get rid of them and manage a test project.
The most common problems are:
- In continuous testing environments, due to time pressure, sometimes Quality focus may be shifted. How can we ensure to stick to the correct mindset even under stress?
- While trying lots of approaches, how can we optimize the best way? How can we decide to go with it? How can we monitor the progress, trends and results of each single POC?
- Test Reliability & Test Smells
Some fundamental solutions are:
- Being truly agile: Adapt new solutions quickly.
- Manage the progress: Be aware of what is going on by setting KPIs to track & monitor with tools like CloudWatch, Grafana
- Technical part: Automation principles for the sake of robustness. Solutions to reduce flaky tests & analysis effort & costs.
- Holistic testing!
Mesut Durukal - Do Bugs Speak?Mesut DurukalQA Automation EngineerIndeed
schedule 10 months agoSold Out!
Do bugs speak?
Yes, they do. People speak different languages like English, German, French, Chinese etc. But is communication to bugs possible? It is important to understand them, because they really tell us something. There is valuable information underlying the defects of a software, and information mining from defects promises for improvements in terms of quality, time, effort and cost.
A comprehensive analysis on all created defects can provide precious insights about the product. For instance; if we notice that a bunch of defects heap together on a feature, we can conclude that the feature should be investigated and cured. Or we can make some observations about the severity or assignee of similar defects. Therefore, there are some potential patterns to be discovered under defects.
Defect analysis is very important for QA people, and especially for QA managers. We utilize lots of aspects to get an idea about the product itself or our procedures. For instance while monitoring defect distribution across testing types, we will discuss how to get an idea about the quality of our testing approach. I.e whether we are applying all types in a balanced way. (functional, performance, documentation, etc.) Or over another graph, in which we track the gap between open defects and resolved defects, we will discuss what action items we can take when the gap widens. Finally, with ML assistance, we will see how we can reduce manual effort and cost.
Results & Conclusion
In this session, we discuss data mining from bugs and usage of ML in defect management. Objective of the study is:
- To present in which ways defects can be analyzed
- To present how ML can be used to make observations over defects
- To provide empirical information supporting (b)
Naoto Kishino - Continuous Security Testing への道Naoto KishinoSET/Quality EngineerLIFULL
schedule 8 months agoSold Out!