Conference DUMP-2014: Section "Testing"
Hello, I am 26 years old and I'm a tester.
I do not want to grow into a programmer, analyst, or manager. I like my work and I want to do it well, but so far it turns out, frankly, not very.
There are lots of interesting ways to learn how to make it better.
The first, but not the best way is to read blogs .
As always, a much more useful thing is books .
Numerous online courses, webinars and master classes of varying degrees of usefulness, from the purely harmful to the incredibly useful, follow the line of books. It all depends not so much on the topic, but on your relationship and the name of the particular presenter.
The most effective way to learn is practice. Even better - practice on different projects. Very good - practice on different projects with more experienced colleagues. Yes, in general - communication with them.
But there is a problem: it’s almost impossible for a tester to work on a new project, and not even a solo (there is a utest for working alone) without changing the place of work.
')
Stand alone conference.
I would not call them an option of learning, rather it is a pleasant way of knowing the world around and finding out - what else should I learn, how does everything work there with people? With the right attitude, utility is incredible.
Testers in the CIS have quite a few conferences. SQA Days for all, Selenium Camp for adherents of automation through the interface, with a dozen smaller events. Happy cities where there were initiative people who created communities.
In Yekaterinburg, testers with conferences are a serious problem.
- We need to get over the abyss in small steps, - we thought and tried to integrate into the existing event.
For several years, one of the few local DUMP conferences has been held in the Urals . Testers have not been represented at it before, but this year it-people - Julia and Elena suggested creating a testing section. That is, to take and just to find interesting topics for conversation and interesting people who have something to tell.
I called friends, they liked the idea and we rushed.
I strongly recommend everyone to engage in such volunteering. The benefits are mass.
First, you will automatically attend the conference.
Secondly, you will get a lot of communication with the speakers, the opportunity to ask any number of questions and find out the whole story. You can even go on a tour.
Thirdly, the ability to select reports, speakers and topics for conversation.
However, you will not strangle the song and you will not kill, each story-teller has his own favorite theme. Only one of the suggested ones was taken by Natalya Rukol natalyarukol , for which she is a special thank you very much. Nevertheless, the volunteer has the opportunity to influence the result. As a result, each section's story is interesting and relevant for me.
At first it was a bit scary.
I know every third speaker from neighboring sections personally. All - practice. Who does not teach at the university, the leader of the community or the creator of the framework.
And here we are with testing.
But then it was thought that all the program speakers around were very smart guys. But we - testers - for some reason, anyway. No matter how clever programmers are. So it will be interesting and we have something to talk about.
Alexander Akhmetov will describe how life works without testers. I fully support this idea in spite of the fact that he himself contradicted it for several years - he was engaged in testing automation, not being a programmer.
Andrei Khitrin will talk about the agony of choosing a testing system framework. I asked him to bring a laptop with an IDE, so that after the story it could be shown to those who want it, how it all works.
Yana Sadovskaya will tell how she answered the eternal questions of testers:
- We finally raise another stand? What rolled out on this stand? How is it, not enough iron?
Mikhail Mikryukov will try, not in general terms, but in terms of numbers and facts, to describe what kind of benefit the tester has done in a single online store, to trace the history from the moment when there was no testing at all, until the moment when testers are already a group.
Tanya Cheremnykh tried to create a tool that helps in a difficult situation when the programmer says:
- I refactored CoreMagicGUIClass there, poke it, nothing broke?
She is a decent person and writes tools, but does not begin to swear (I would swear ) .
Ilya Vakhrushevwent from hand to hand as an outsourcer-tester-automation and managed in this role to visit various projects, and he will tell us how to use outsourcers correctly.
And, as I said, Natalya Rukol will talk about how testing lives completely without testers.
I hope, the section will turn out not absolutely normal. Through it, the refrain - the first and last report - will pass the idea that the correct tester as the correct interface is missing, but his work is being done.
Senior comrades suggested to me that the testing section should have some idea. it should sound something other than the general words: "quality", "regression" and "planning."
I would like us to find out what the manual tester should and can do, except and in addition to direct trampling.
I would like my friends to tell me - and then on the sidelines talk to the guests about a specific job that can be done by a tester-specialist at the company and from which there will be no harm, and there will be a definite benefit.
I would like to see you as test and development specialists and argue with you about all this.
Come.
I do not want to grow into a programmer, analyst, or manager. I like my work and I want to do it well, but so far it turns out, frankly, not very.
There are lots of interesting ways to learn how to make it better.
And what are the options?
The first, but not the best way is to read blogs .
As always, a much more useful thing is books .
You are of course interested in my opinion of them.
- Kaner, Software Testing - Mastrid for a Tester of Products Living for More than a Couple of Years
- Culbertson, Rapid Testing - Not at all Rapid, but Still Testing
- Myers, The Art of Testing Programs - see Quick Testing
- Whittaker How to test in Google - a really good book book about the right mood and attitude to work
- Dustin, Automated Software Testing - if you are serious about automation
- Beizer, Testing the black box - raise your hands, who read to the end and understand everything? Nevertheless, there is a mass of useful
- Messarosh, xunit Test Patterns - if you're dealing with code, then Mastrid. If you do not want to deal with the code, then all the more
- Kaner, Lessons Learned in Software Testing - in my opinion, the best book about testing
- Savin dot-com testing is the starter kit of any tester. It is a pity, but they often forget that this set is exactly the starting one and if after a couple of years of work the set has not changed it is very sad
- Kaner, The Domain Testing Workbook - in my opinion, the world's first testing guide
- Black; Key testing processes - tediousness and I do not believe that this happens
- Tamre, An introduction to software testing is tedious, but I believe that this is exactly what happens.
- Crispin, Flexible Testing - together we repeat the mantra "and we are happy!"
Numerous online courses, webinars and master classes of varying degrees of usefulness, from the purely harmful to the incredibly useful, follow the line of books. It all depends not so much on the topic, but on your relationship and the name of the particular presenter.
The most effective way to learn is practice. Even better - practice on different projects. Very good - practice on different projects with more experienced colleagues. Yes, in general - communication with them.
But there is a problem: it’s almost impossible for a tester to work on a new project, and not even a solo (there is a utest for working alone) without changing the place of work.
')
Stand alone conference.
I would not call them an option of learning, rather it is a pleasant way of knowing the world around and finding out - what else should I learn, how does everything work there with people? With the right attitude, utility is incredible.
I want to tell a story about this very proper attitude.
On SQA days, my employer carefully sent me and several colleagues, and everything was perceived as a holiday and a movie to be shown to us. But once I had to pay most of it personally and go alone. And everything just changed.
The motivation to pull out all useful knowledge from the speakers is enormous, not a single couloir was left unvisited, not a single narrator was left without a question. The absence of a number of colleagues - a powerful impetus to make new acquaintances. Personal requirements for reports also grow up - one feels the need to recapture every ruble spent.
Correct attitude to the conference is when you know exactly with whom and what you would like to talk about, what to learn. Reports are a reason for conversation, for further work.
The motivation to pull out all useful knowledge from the speakers is enormous, not a single couloir was left unvisited, not a single narrator was left without a question. The absence of a number of colleagues - a powerful impetus to make new acquaintances. Personal requirements for reports also grow up - one feels the need to recapture every ruble spent.
Correct attitude to the conference is when you know exactly with whom and what you would like to talk about, what to learn. Reports are a reason for conversation, for further work.
Testers in the CIS have quite a few conferences. SQA Days for all, Selenium Camp for adherents of automation through the interface, with a dozen smaller events. Happy cities where there were initiative people who created communities.
In Yekaterinburg, testers with conferences are a serious problem.
Dump
- We need to get over the abyss in small steps, - we thought and tried to integrate into the existing event.
For several years, one of the few local DUMP conferences has been held in the Urals . Testers have not been represented at it before, but this year it-people - Julia and Elena suggested creating a testing section. That is, to take and just to find interesting topics for conversation and interesting people who have something to tell.
I called friends, they liked the idea and we rushed.
I strongly recommend everyone to engage in such volunteering. The benefits are mass.
First, you will automatically attend the conference.
Secondly, you will get a lot of communication with the speakers, the opportunity to ask any number of questions and find out the whole story. You can even go on a tour.
Thirdly, the ability to select reports, speakers and topics for conversation.
By the way, I suggested these speakers:
- architecture of automation, what needs to be done, and in no case, assessment of terms, proper interaction with developers and programmers, what and how to test and not test automatically
- place of manual testing in the development cycle - how not to increase the time
- effective testing without a tester - organizational and technical ways
- organization and conduct of alpha and beta test
- how to deal with bug driven development
However, you will not strangle the song and you will not kill, each story-teller has his own favorite theme. Only one of the suggested ones was taken by Natalya Rukol natalyarukol , for which she is a special thank you very much. Nevertheless, the volunteer has the opportunity to influence the result. As a result, each section's story is interesting and relevant for me.
At first it was a bit scary.
I know every third speaker from neighboring sections personally. All - practice. Who does not teach at the university, the leader of the community or the creator of the framework.
And here we are with testing.
But then it was thought that all the program speakers around were very smart guys. But we - testers - for some reason, anyway. No matter how clever programmers are. So it will be interesting and we have something to talk about.
Speakers
Alexander Akhmetov will describe how life works without testers. I fully support this idea in spite of the fact that he himself contradicted it for several years - he was engaged in testing automation, not being a programmer.
Andrei Khitrin will talk about the agony of choosing a testing system framework. I asked him to bring a laptop with an IDE, so that after the story it could be shown to those who want it, how it all works.
Yana Sadovskaya will tell how she answered the eternal questions of testers:
- We finally raise another stand? What rolled out on this stand? How is it, not enough iron?
Mikhail Mikryukov will try, not in general terms, but in terms of numbers and facts, to describe what kind of benefit the tester has done in a single online store, to trace the history from the moment when there was no testing at all, until the moment when testers are already a group.
Tanya Cheremnykh tried to create a tool that helps in a difficult situation when the programmer says:
- I refactored CoreMagicGUIClass there, poke it, nothing broke?
She is a decent person and writes tools, but does not begin to swear (I would swear ) .
Ilya Vakhrushev
And, as I said, Natalya Rukol will talk about how testing lives completely without testers.
Hopes and dreams
I hope, the section will turn out not absolutely normal. Through it, the refrain - the first and last report - will pass the idea that the correct tester as the correct interface is missing, but his work is being done.
Senior comrades suggested to me that the testing section should have some idea. it should sound something other than the general words: "quality", "regression" and "planning."
I would like us to find out what the manual tester should and can do, except and in addition to direct trampling.
I would like my friends to tell me - and then on the sidelines talk to the guests about a specific job that can be done by a tester-specialist at the company and from which there will be no harm, and there will be a definite benefit.
I would like to see you as test and development specialists and argue with you about all this.
Come.
Source: https://habr.com/ru/post/214857/
All Articles