Quality Control of BigData projects
Last days the more often you can meet news or blogposts regarding Big Data projects, technologies, specialists and so on.
Working in outsourcing company I see high demand from our partners on engineers who can provide solutions that will ensure the quality of such systems.
This presentation, let’s say inrodactionary speech regarding the topic. I’d like to talk why we are going to speak about quality control rather than just testing; what are main directions of work there and which skills are needed to be a Quality Engineer on Big Data project.
Data Pools - an approach to manage test data
Data Pool is a configurable test automation supporting tool which fetches data from known data-sources and provides a way to query the data which is safe to be used by tests.
How to stop fearing and start automating. Or not to start
On previous conference I was asked: "How to understand whether test automation will be successful in our project or not?"
"Well" - I started, and understood I did not have a simple answer. That is why I decided to bring all my thoughts together and prepare this talk.
Actually for me, who is automating different test activities for the last 12 years, it's hard to understand why people have doubts, why they have a question "to automate or not to automate?" So we continued to discuss this on the regular meetup of SPb testing group. Then I spoke with people who work in companies where test automation does not rock.
As result I have something to talk about now. The goal is to create a kind of checklist answering which everyone will get YES or NO for or against automation and clear understanding why.
UICov - UI-tests coverage analysis tool
"- Hey, testers! What is the coverage of these tests?
- What 'cucumber'?
- But what 'coverage'?"
(c) Табличка “Сарказм” (https://twitter.com/glorphindale)
Do you remember my presentation I did on SQA Days conference about an year ago "Visualization of UI autotest coverage" (http://sqadays.com/en/talk/26051)? It was about our idea how to measure coverage of UI tests. Also I promised to prepare an opensource version of the tool.
Here it is: https://github.com/budabum/uicov.
I'm going to familiarize you with this tool and provide "getting started" hints to help you to use UICov to measure coverageof your tests. The tool is cross-platform and independent on programming language.
The plan is:
1) To give an overview of the UICov tool.
2) Demonstrate some features and asic examples of how to use it.
Also I'd like to raise a question why lots of people misuse PageObject.
Let's talk about test data
The most complicated part of testing is preparing test data. The data depends on type of testing, its target as well as from development phase and number of other factors.
Should we write data generator or create artificial stuff manually? Should we find some data in copy of production database or it’s better to create a specific test subset? Should we use random or static data? These and other similar questions will be discussed here.
Besides the technical questions there are organizational or infrastructural issues. For instance you may have lack of permissions or it’s impossible to use stub on test environment.
And one more question: how you are sure that you are really use the data you were intended to use?
It won’t be a presentation. It’ll be a conversation with you, colleagues. I do not have answers on all the questions but may be you have? Let’s gather and discuss this topic.