TestCon Vilnius 2017
TestCon Vilnius 2017 – одно из ведущих событий, в первую очередь предназначенное для встречи специалистов по тестированию и анализу результатов тестирования программного обеспечения, инженеров по качеству, разработчиков и всех, кто хочет научиться лучшим рабочим практикам и внести свой вклад в развитие плавного цикла разработки и обеспечения качества ПО. Конференция является отличной площадкой для ознакомления с новейшими тенденциями отрасли, обмена опытом и получения выгодных возможностей совместной работы.
- Специалистам по автоматизации тестирования
In the end your software will be used by multiple people. But how do you know these end users can or will actually use your product? What do you actually know about this user and how to optimize your software for this users? In this session I take you on a journey on how we got to know your customers. You will learn about 8 cheap or even free practices you can use to learn to know your customers and en users and improve your software with it.
Being an Agile Tester can be really challenging. I would like to share with you experience from two types of company cultures – outsourcing and startup worlds to help you understand context-driven agile: you introduce testing in different ways in different agile organizations.
In the last couple of years, I had a chance of working both in an outsourcing company and in an emerging startup. Things that you read about Agile or Lean philosophy are nice in theory, the practice can be quite different. What are differences between these approaches?
You will be presented how teams I have worked with in outsourcing and startup company implemented different methodologies to get to the same goal – deliver the quality product. We have mostly used Scrum and Kanban but adapted them to fit our needs. Each approach has brought new tasks, tools and learning opportunities for me as a software tester on a team. What are challenges when the context is switching fast, and how to adapt to those changes?
Join me for learning from my experiences how testing in agile can be different and pick the pieces that fit your current situation.
-Learn what does it mean to be an Agile tester in any context: Agile or Lean, Scrum or Kanban;
-Understand the basics behind the practices that could be applied in your company;
-Learn how to overcame challenges for a software tester when the context is switching fast.
On the example of Game of Thrones TV series it will be shown how to organize the process for the continuous delivery and use the best practices in logical organization to ease the testing. All the helpful testing tools will be specified to help in such an organization.
There are tons of talks on how to build automation properly, however there is no silver bullet for every problem and here’s where people get in trouble. They can’t apply the “perfect” approaches and practices so they try to implement their own and often make common mistakes.
Candy Crush Saga is one of the biggest mobile games today with more than 1000 levels of difficulty—and users continue to ask for more. When building new content, it is extremely important to ensure that the level of difficulty is balanced and that the user does not experience crashes or problems through some unforeseen level of play. Alexander Andelkovic shows you how King is training artificial intelligence (AI) programs (bots) to test its games by mimicking human interactions. Join Alexander as he discusses how King is taking testing to the next level by employing Monte Carlo Tree Search, automatic heuristic construction, and NeuroEvolution of Augmenting Topologies (NEAT) to train bots to test and evaluate difficulty levels. He discusses ways to extend and use AI bots to predict game success rates and conduct automatic performance testing. Alexander explains how this AI approach can be generalized to test other applications. Learn how AI can help you with testing that’s getting very difficult to master with traditional testing techniques.
Testing is a complex activity, involving many decision points and multiple possible approaches to the same end goal, that of ensuring the most useful information is provided about the tested software.
At the same time, nature is also complex, and an inspiration source for some very useful models, such as Cynefin. This sense making and context determining model is quite popular in the agile practices world, and can also be a good candidate for testing.
Is test automation the best approach? Should automation alternatives be considered? Should I build or buy my testing solution? These are some of the questions that people involved in testing are facing many times, and that can be made easier to answer to with the help of the Cynefin framework.
My session reveals how Cynefin can be used to make sense of the testing context, thus helping determining the most suitable approach for testing.
At the same time, since Cynefin is not a static model, the session highlights how the testing context is or can be changed, updating accordingly the testing approach.
– Awareness of the context challenges for testing
– Introduction of the Cynefin framework
– Mapping testing strategies to Cynefin complexity domains
– An example for supporting the “no-automation” decision”
The accessibility testing wasn’t on the focus of the testing community for a long time among the other non-functional testing activities. This situation has rapidly changed through these past few years and the topic is at its heat right now.
It was triggered by the political force, suggesting everyone must have access to online public services. There was a deadline set for the change to be implemented in Europe, US and Canada by 2020. Now the demand is at its peak and so is the global testing community regarding the topic.
My presentation will cover the accessibility testing techniques and the lessons learned, based on the projects, done for a large financial institution, facing the altering situation.
It will also focus on why and how do we improve on the issue as well as give practical tips and tricks how to perform it in a more efficient way and which mindset should we have by assuring the accessibility of our projects.
When you are writing Selenium tests to check for elements on your page, by taking the classic approach (checking for each element’s properties at a time), you might get to a large number of assert steps. This increases the lines of code your tests have, make the tests difficult to maintain and tricky to read.
Wouldn’t it be nice if the actual checking part of the test would be small, perhaps one line of code? Pip Corina uses this approach so you’ll be able to take it too! Hence your tests will be small and clean. All you will need to do is model the pages/modules/items by using an Object Oriented approach.
Shift Left, Shift Right and Improve the Centre - A Strategy for Testers in Continuous Delivery context
The technology world is changing fast, faster than ever. A few years ago we thought that only the Amazon(s) or Facebook(s) of this world would do continuous delivery, now the phenomenon is getting traction, starting to become mainstream and soon it will be commoditised. Everybody will do it.
Why, you might ask? Because the ability to release often gives organisations an edge over the ones that have a slow turnaround. For an example, you only have to look at the disruption happening in the financial industry, where billions of dollars are being invested by venture capitalists on startups that will replace the banks of today.
As testers we can either hide our head in the sand and hope it all goes away, or try to understand what the change means for us, embrace it, and build the skills we require to thrive.
In this interactive talk you will learn about the challenges that continuous delivery brings to testers, you will discover opportunities for testers that are within your current domain and brand new dimensions where today’s testers can be extremely valuable tomorrow.
You will leave this talk with a checklist of skills and tools you need to start learning. These skills will give you an edge over the competition and will allow you to become much more valuable when the change finally knocks at your door.
An often overshadowed aspect of building great products is ensuring these products are reliable and perform as expected. Similar to physical products, the quality of a digital product has a large impact on the customer/user experience. Typically, a quality assurance (QA) or testing team leads this effort. But, what is the difference between QA and testing, and does it matter?
The reality of testing frontend code is dark. React and other modern frameworks now enable us to write unit tests that test each component separately. But what if I want to test components together? If I want full interactivity, including Ajax calls? Today, the only recourse is to do browser automation testing, which are considered painfully slow, difficult to write, and flaky.
Today, in 2017, we finally have enough tools in our belt to have an alternative to browser automation. This alternative enables us to simulate a browser inside Node, and run your frontend code fully under Node. Incredibly enough, this is not too difficult to do.
I will be covering:
– Unit, integration, and end to end tests today
– The drawbacks of the current methodology
– Simulating DOM and the browser
– Writing tests using this simulation
– Adding full interactivity and Ajax call mocking to these tests
– And, finally, a poem!
Performance and scalability are core quality attributes of any system; unit testing, integration testing, UI testing, they all focus on functional requirements. Good performances mean happy users, less resource usage which translates to lower running costs (power, cloud bills) and customer retention.
In this session we will recall some basic concept of performance testing and demonstrate by adding specific test to an VSTS build of a simple ASP.NET Core application running on Azure.
Code quality is a first step in considering the other dimensions of software, like maintenance or security.
Performance and scalability seem old school or tightly related to a specific technology stack, but they are not.”
The PHP stands aside from all Selenium world. Unlike other PHP doesn’t have an official Selenium implementation, however PHP is still used at 80% of Internet websites. How would you test PHP application? Today you would probably choose Codeception testing framework (5M installations), which is scenario-driven BDD style acceptance testing framework with Selenium support. From this talk you will learn how to write test scenarios, with PageObjects, Depenency Injection, DataProviders and other tools to make your PHP tests compact and explicit.
Behaviour-Driven development, BDD, is a three-step procedure that lead us to implement the right software. I will show you the three parts:
* Discovery – find out what we should create
* Formalization – capture unambiguous examples that describe what we should build
* Automation – run those examples as automated acceptance tests
Our goal is to understand what our users want, formalize examples describing our current understanding, and finally automate the testing of the implementation. Each step is easy if done properly. The result? Software that supports our business while making the life of both users and developers better.
Machine Learning is on hype. But we don’t see many real valuable example of it. Testing and Test automation is the step one, where AI in development can start. Talk will describe our experience in ReportPortal with adaptation of Machine Learning. And present it functionality and how it can improve your test automation
Real Quality Assurance from an Agile and Lean Viewpoint: Are you ready for real software and test engineering?”
Traditional testing, as a means towards quality assurance, is far too costly and far too ineffective. There are much smarter ways to approach software quality. One problem is who will lead the change process? This talk will outline a far more advanced QA function, and challenge CIO and CTO levels of management to implement it. ‘Agile’ simplified, means ‘ability to learn quickly and change fast’. ‘Lean’, simplified, means ‘focus on Value and avoid non-value bureaucracy’.
We are automating web applications using Selenium WebDriver. It is easy to get started with automated tests. It is harder to maintain an automated test system. The entropy increases with time and different developers/testers; your once beautiful crafted test code may end up unrecognisable.
The cure for this is to apply the Four Rules of Simple design while you maintain the tests. The rules, as suggested by Kent Beck, are:
* Test pass
* Express intent
* No duplication
Thomas will take a test suite for a web application and by following the Four Rules of Simple design, transform it step by step into something that is easier to maintain.
This will be a live coding session with a lot of refactoring. All steps will be small and you will therefore be able to follow even if your main profession isn’t writing code. After this session, you will know that even the most horrible test code is possible to clean up just be slowly transforming the code in small steps.
Where can testers fit in in the DevOps culture that is eating the software world? Where does testing fit in a continuous delivery pipeline? Compliance pipelines? Security pipelines? All these and more will be covered in this session by Roy Osherove.
During the last 10 years I have worked on 4 different test automation projects in 4 different companies. According to MY expectations none of these projects have been successful. Why? Because something was forgotten, eliminated from the origin plan or implemented incomplete or even wrong.
When taking over the responsibility for my current test automation project, my boss has given me 2 years time and enough resources to do it right. With the lessons learned of the previous projects we found 11 key players to be nominated for our test automation team to get it up and running – and to be able to play in the Champions League!
The presentation shows how to set up the defense to have it simple, robust, maintainable and always up and running. The midfield makes it effective, adoptable and understandable. And Test Automation can be even – and has to be – offensive: Target-oriented test runs get the most out of the automation and with diversion the test automation is able to detect new bugs. Internal and external promotion provides support and motivation.
The own team has to be world-class, as also the “opponents” have good players: How to detect attack attempts and how to block them?
Finally our “course of the match” is presented: What has happened before the kickoff, during the 1st and 2nd half time and in the extra time?
All the 11 key players and the opponents are presented with anecdotes and proven with the practical background of our test automation framework.
Reflecting on my daily task and how to keep growing, I discovered that different task, required different lenses, viewed at different angles, with different mindset. Hence to effectively test, I need to tweak my mindset for different task. To achieve this, I need to keep my mindset flexible when I test. To keep my mindset flexible and help me look at things from different angles, I put a label on the mindset approaches that I find useful. Over time, my way of reasoning evolved into a set of tools that I refer to as “My Mindset Toolkit”.Using real life test stories, I will present to you examples of mindset tools that I have identified, how I have used them to optimize collaboration in software development teams, become a valuable team member and a skilled tester. I will further propose a model that can help individuals develop their own mindset tools depending on the type of environment and product being developed.Examples of Identified Mindset Tools are: “User”, “Already Tested”, “Curiosity”, “Analytical”, “Lazy Tester”, “Communicator”, “Bug Conviction”, “Trust”, “Business” and “Team leading” Mindset Tools.Key takeaways
You will learn about Mindset Tools; a cheaper and effective way to develop a test mindset and enhance testing skills. Mindset Tools are developed from test stories, therefore it’s easy to visualize yourself in the scenarios being described and easy to learn and apply.You will be inspired to be innovative and creative towards your observations and reflections.Mindset Tools can help enhance your skills in both the technical and human aspect of testing and releasing of a quality product.You will learn how to develop your own Mindset Tools and become more valuable in your role as a tester, programmer, test or project manager.
In this talk, Kristel will share with us how connectivity and mobility will redefine testing quality of mobile apps in the future.
For some reason, people not involved with the field of UX (usability) have the idea that usability testing in general is as difficult as rocket science—especially for mobile and the constraints it comes with.
I hear from people that the main reasons for not conducting usability tests are that they don’t have the know-how, “enough” time, and, most commonly, the budget. Of course, some approaches can be very difficult, take a lot of time, and be very expensive. But they don’t have to be. With this session, I will discuss some of the approaches we (as Keytorc) use for usability testing to keep all these factors as low as possible. I’ll also address how mobile usability testing differs from desktop usability testing.
Hopefully, the attendees will leave the session with an understanding of how to choose their usability testing approach and how to select their targeted users, test scenarios, and usability testing tools.
Basics about exploratory testing:
• Terminology and techniques
• Test sessions
• Exploratory testing from management and competence development point of view
• Contexts, where exploratory testing is most useful
• How to develop one’s learning and thinking skills to enable exploratory testing
• Skill to question, skill to analyze, skill to assess one’s own activities etc.
• Exploratory Testing in the future, where does it belong, where does it fit?
Testers should not be debuggers. Testers should not get bad work dumped on them. Even if you don’t believe we should be kind to testers; the entire project will take less time, and have more quality, if we do not mistreat the test function. We must not make testers the scapegoat for our upstream bad development processes. To clarify this position I offer a – Testers Bill of Rights.
1. Testers have the right to sample their process inputs, and reject poor quality work (no entry).
2. Testers have the right to unambiguous and clear requirements.
3. Testers have the right to test evolutionarily; early as the system increments.
4. Testers have the right to integrate their test specifications into the other technical specifications.
5. Testers have the right to be a party to setting the quality levels they will test to.
6. Testers have the right to adequate resources to do their job professionally.
7. Testers have the right to an even workload, and to have a life.
8. Testers have the right to specify the consequences of products that they have not been allowed to test properly.
9. Testers have the right to review any specifications that might impact their work.
10. Testers have the right to focus on testing of agreed quality products, and to send poor work back to the source.
Организационный комитет: DATA MINER LABS, email@example.com, 1