Ever faced yourself doing laborious and repetitive work as a tester? well of course you have.
In our day-to-day work we have to perform manual tasks before, during, and
after testing.
Copying files from folders into other folders, possibly spread out on different servers?
Looking for specific text strings in log files, matching those to other text strings and timestamps in other log files.
And let us not get started on generating new and unique test data, manually typing it in.
Day to day work includes some or all of these tasks, and there might be many more that you perform over and over again without you even thinking about it anymore.
Not only does it take time away from us, it is also mind numbingly boring at times, and it is easy to make mistakes when we have long lists of things to do.
But who says it has to be done by you?
In this workshop I will show participants how easy and quick small yet simple and powerful help tools can be written in Python that assist you in your everyday test life.
Participants will of course learn the basic syntax of the programming language, how if/else-statements work, create loops, methods, classes and more.
We will learn how to get started with Python, writing the very first script and tool, and from there we embark on exploring the oh so powerful, but ever so elegantly and easy to use libraries that are included in a Python installation out of the box.
The examples will be easy to follow, but useful for any tester in their day to day work, and we will have fun as well.
I hope to have inspired you by the end of the workshop to look into using Python yourself in you day-to-day work.
Many software systems are required to process huge combinations of input data, each of which deserves to be tested. Since we rarely have time to create and execute test cases for all these combinations, the fundamental problem in testing is how to choose a reasonably-sized subset that will find a large percentage of the defects but that can be performed within the limited time and budget available.
Pair-wise testing is the most effective test design technique to deal with this problem but, unfortunately, is not understood by many testers. The answer is not to attempt to test all the combinations for all the values for all the input variables but to test all pairs of variables. This significantly reduces the number of tests that must be created and run while still finding a large percentage of the defects. Lee shares examples of the effectiveness of pair-wise testing and demonstrates this technique through the use of orthogonal arrays, James Bach’s all-pairs algorithm, and Microsoft’s PICT tool. Learn to apply this technique through a number of hands-on exercises.
The tutorial takes the form of short ½ day security test of a deliberately insecure web application; we will start the day by reviewing the application to understand what and how data flows within the system. We will then conduct a series of practical exercises to explore the security of the system from the following perspectives: Data at Rest, Data in Transit and Data on Display. As we examine each of these perspectives we will cover the appropriate Security background theory, tools and techniques and then apply these to the application to uncover any issues. As we identify security issues we’ll examine the issues around reporting security problems.
The session will be a fun and highly practical one where we will cover a range of security testing techniques including common techniques such as Cross Site Scripting, Code Injection, Request Forgeries. We will also start building your security testing toolkit from freely available tools.
At the end of the day, the attendees will have:
- An understanding of how to approach security testing from the perspective of a tester.
- An understanding of the OWASP Top 10 vulnerabilities.
- Practical experience of some of the key techniques and tools used in security testing.
- A workbook containing additional practical exercises to try once the workshop is over.
This course is suitable for any tester and test leads who is looking to extend their skills into security testing. No prior experience of security testing is required but a curiosity and interest in the topic is essential. The course will focus primarily on testing the security of web applications so a basic understanding of HTTP and SQL would be useful.
The first principle of context-driven testing is: "The value of any practice depends on its context." James Bach defined context in his keynote at Let's Test in 2013 as "All the factors that significantly influence the problems and solutions that lie within the scope of their mission.”
How do you analyze your context? What factors are influential and how do you model these? And once you know your context how do you use this information to adjust your testing to this context?
In this interactive and challenging track you will find out what context means and what factors matter.
We will also learn how models like the heuristic test strategy model from Rapid Software Testing and visualization techniques like "the product ecology" developed by Ruud can be used to resolve this context analysis problem.
You will find that factors you haven't anticipated may play a unexpected role while you are testing your product.
Sources:
• https://www.satisfice.com/tools/satisfice-cm.pdf
• https://www.ruudcox.wordpress.com/2013/10/25/an-example-of-a-product-ecology-for-testers/
Why is testing low status?
In many software development projects it’s common to hear jokes such as “testers are programmers who can’t code” or “testers are failed programmers”. Sometimes people refer to testers as “just testers”. It almost seems like testers have a different status, a lower social status than a typical developer. Is this true? And if true – why is it like this?
With a short presentation of my personal and professional experience in software testing I invite you to discuss this tabooed topic.
I am looking forward to see you all!
Many software systems are required to process huge combinations of input data, each of which deserves to be tested. Since we rarely have time to create and execute test cases for all these combinations, the fundamental problem in testing is how to choose a reasonably-sized subset that will find a large percentage of the defects but that can be performed within the limited time and budget available.
Pair-wise testing is the most effective test design technique to deal with this problem but, unfortunately, is not understood by many testers. The answer is not to attempt to test all the combinations for all the values for all the input variables but to test all pairs of variables. This significantly reduces the number of tests that must be created and run while still finding a large percentage of the defects. Lee shares examples of the effectiveness of pair-wise testing and demonstrates the technique through the use of orthogonal arrays, James Bach’s all-pairs algorithm, and Microsoft’s PICT tool - and gives you a good introduction to this GREAT technique.
Håkan explains why testers need to understand why companies really invest in testing. By asking the right questions and providing insights of how the product really works, the tester can become an invaluable asset to the development team and external stakeholders. Product owners for example do care great about their product and the cost and time constraints involved, not always about how the product is built. They do have the right to ignore this process and we as testers can learn how to assist in bridging this gap and build market awareness in the team. Without understanding the business value a tester provide, or could provide, the tester is simply not reaching his or hers full potential as a professional tester.
Key learning outcomes
* Companies does not really care about quality, they care about the outcome that a certain quality level provides
* Testers need to start reporting the business value of the product under test because they are in a unique position to do so.
* How concretely can testers increase their business value? Some examples:
– Really understand the company providing the product
– Understand the problems the product should resolve
– Understand personas and their relationship with the product
– Build market awareness in the team
Testers and businesspeople rarely interact until a business limitation emerges that affects testing. Likewise, testing could find vulnerabilities that affect the course of the business. Either way, Pradeep and Jon think there's some lessons in exploring this relationship.
In this authentic role play based on each of their years of experience with managing testing services companies, they'll walk you through 5 aspects of a burgeoning context-driven relationship. A client who wants testing will meet the leader of a testing service company, eager to show how it is different than the rest. Their aim is to frame real scenarios that could lead to revelations about context-driven thinking.
Part 1: "The Intro" -- a conversation on values and mission
Part 2: "The Handshake" -- an agreement on principles and tactics
Part 3: "The Results" -- delivery and scrutiny
Part 4: "The Follow-Up" -- making adjustments to improve value
Part 5: "Now What?" -- testing the relationship
Much like jazz musicians jamming on stage, the conversations between Jon and Pradeep will not be scripted, but in recreating these “conversational conditions”, their hope is that it will enable you to discover the same kinds of epiphanies of context-driven thinking that come from real-time exchanges.
A leader sets an example and inspires others to follow and then to lead in their turn. You don’t have to be a manager to be a leader—but if you’re not also a leader, you can’t be a good manager.
• What does it take to be a leader?
• Where do exceptional test leaders focus their energies?
• How can you get to be an exceptional test leader?
• What special skills or personal qualities distinguish a context-driven test leader?
Inspiring testing means much more than getting a team to follow you. It means setting an example with excellent work. It means helping others to grow their leadership capabilities and fostering teamwork that will enhance the effectiveness of your whole project team. It also means earning credibility, so that managers and fellow team members understand the value that context-driven testing delivers, and the importance of the information your testing uncovers. You can shine as a context-driven test leader even if you are the only tester on your project team.
In this full-day interactive workshop, we’ll examine the key focus areas for test leaders, and work together to identify the skills and personal qualities essential for exceptional test leadership.
You’ll have an opportunity to practice solving leadership problems, to assess your leadership aspirations and potential, and see how you can become the leader you want to be and bring benefits to all the projects you work on.
This workshop is for testers, test managers, test leads—anyone who wants to become a leader or a more effective leader.
