Problem identities among testers

 3r33856. 3r3-31. Problem identities among testers 3r33841. 3r33838.  3r33856. The following are problem individuals in the quality assurance department (QA): 3r3-3830.  3r33856. 3r33838.  3r33856. 3r33832.  3r33856.
3r33655. Fire hose
3r33842.  3r33856.
3r33750. Prosecutor
3r33842.  3r33856.
3r33434. Alarmist
3r33842.  3r33856.
Scientist 3r33842.  3r33856.
3r3306. Misleading
3r33842.  3r33856.
Oppressed 3r33842.  3r33856.
Random clicker 3r33842.  3r33856.
3r33526. Blithely cheeky
3r33842.  3r33856. 3r33844. 3r33838.  3r33856. alarmist 3r33842.  3r33856.
Dangerous in conjunction with a project manager ...
+ 0 -

Unpleasant errors while writing unit tests

 
3r3-31.
The other day I will be doing an internal report in which I will tell our developers about the unpleasant errors that may occur when writing unit tests. The most unpleasant errors from my point of view are when tests pass, but at the same time they do it so incorrectly that it would be better not pass. And I decided to share examples of such errors with everyone. Surely something else tell me from this area. Examples are written for Node.JS and Mocha, but in general these errors are true for any other ecosystem. 3r3640. 3r33535.  
To make it more interesting, some of them are framed in ...
+ 0 -

Reasonable pair testing

 3r3406. 3r3-31. 3r33393. The authors of the November "Tester's Calendar" 3r3144. Olya Fazulzyanova, Tester Kontur. Extern, and Olya Izyurieva, Tester Kontur. Billing and organizer of the course testers. The girls spoke about the pair testing, the tasks it helps to solve, and gave an example of the unsuccessful use of the practice. 3r33394. 3r3333391.  3r3406. Reasonable pair testing XP There is a practice - pair programming. In many sources it is written about the mass of its advantages: high quality code, interchangeability of developers, etc. 3r33394. 3r3333391.  3r3406. 3r33393. If pair programming is so efficient...
+ 0 -

“It was believed that the code will replace the UML diagrams, and it will not be necessary to test”: an interview with Alexey Barantsev

“It was believed that the code will replace the UML diagrams, and it will not be necessary to test”: an interview with Alexey Barantsev  
 
Alexey Barantsev Probably one of the most famous people in Russian testing: he is known also from 3-33111. software-testing.ru
, and on 3r3133. selenium2.ru
, and by participating in Selenium WebDriver, and not only. At the same time, he is also one of the most experienced: he has been in testing since 1994. And when it became known that he would speak at our Heisenbug conference from 3r-3254. report r3r3257. "The zamorochki in Selenium WebDriver", we wanted to ask such a speaker. We started with questions about how testing in the 90s differed from today's, and then turned to modern realities.
 
...
+ 0 -

Development through testing: improving skills

Testing is an important skill that every developer must possess. However, some do it reluctantly.
 
 
Each of us came across a developer who claimed that tests are useless, they require too much effort, and indeed his code is so excellent that no tests are needed. Do not believe. Testing is extremely important.
 
 
Development through testing: improving skills
 
 
Tests make your code more stable and reduce the number of bugs. It seems to you that this is not the case, because you know every bit of your code. After all, you wrote it, why else tests?
 
 
Suppose you are creating an application for the weather. You wrote the code a few days or weeks...
+ 0 -

“To make changes, understand why people resist them”: Jim Holmes on the culture of testing

“To make changes, understand why people resist them”: Jim Holmes on the culture of testing
 
 
What could the army teach the tester? What are the two extremes in testing approaches? How to explain that technical debt payment is red? What do the previous questions have in common?
 
 
The general thing is that for all their difference, they are all close to one person. At Jim Holmes behind several decades of IT experience, which began in the 80s in the US Air Force - it is not surprising that he is ready to tell a lot. The concept of “testing culture” is important for him, and we asked him questions that can vary greatly, but in the end, one way or another, they are connected with the testing ...
+ 0 -

"Find N Differences." Experience testing layout Tinkoff.ru

+ 0 -

Testing an application on Go as a black box using Rspec

Testing an application on Go as a black box using RspecWell-written tests significantly reduce the risk of “breaking” the application when adding a new feature or fixing an error. In complex systems consisting of several interrelated components, the most difficult is to test their points of contact. 3r33320.  
3r33320.  
In this article I will talk about how we faced the difficulty of writing good tests when developing a component on Go and how we solved this problem using the RSpec library in Ruby on Rails. 3r33320.  
3r311. 3r33320.  
3r33333. Adding Go to the technology stack of the
project. 3r33320.  
One of the projects, which is developed by ...
+ 0 -

Alert Lida: Security Testing Automation

Good afternoon, dear readers. My name is Victor Burov, I am a developer in the ISPsystem. In the last post I talked about tool for creating autotests , today I will share the experience of automating security testing.
 
 
Alert Lida: Security Testing Automation  
 
At first, an individual employee was looking for vulnerabilities in our products. Manual testing took a lot of time and did not guarantee that all vulnerabilities would be found. Having found out the basic laws of testing, we came to the conclusion that it can be automated. Then we decided to write a utility that will facilitate the life of the tester, save his time and allow ...
+ 0 -

 [Bug bounty | mail.ru]Access to the admin panel of the partner site and the disclosure of data of 2 million users

 [Bug bounty | mail.ru]Access to the admin panel of the partner site and the disclosure of data of 2 million users  
 
Relatively recently, I switched from searching for vulnerabilities on random sites to Bug Bounty sites, and for many such a choice seems obvious - in such programs, a researcher in 90% of cases will receive not only good experience, but also a guaranteed reward for valid vulnerability, while random site can stumble upon misunderstanding and threat. Actually, in order to gain reputation and “acceleration” on the largest Bug Bounty - HackerOne, it was decided to focus on finding vulnerabilities on one of the major bugbounty programs - mail.ru.
 
 
This article will deal with several bugs at mail.ru itself...
+ 0 -