Тестировщик

During my work I gained theoretical knowledge on all these items and while working on projects I had the opportunity to implement and improve my knowledge about:
- Regression testing. Every two weeks I carried out regression testing on all the projects. Regression testing usualy included; smoke testing, test cases failed in the past, test cases for basic functionality, frequently and heavily used features, critical for business features, bad fixes test cases.
- Exploratory/Ad-hoc testing is also the kind of testing that I used very often as sometimes there was little time after the developers finished the implementing of new features and the day of the release. Considering the fact that the CSS project is very large and it was impossible to do it alone in a short period of time I had to test only those features which had been affected in this or that way.
- Domain/Function testing. There were a great number of fields , especially in Content Admin application (different filters, creation of rules , publishers, batch loads, etc) and I had to use domain testing, The same kind of testing was implemented when I tested the values of different fields in rests.
- Testing complex logical flow was supposed to be implemented while testing the rules in Content Admin aplicatons. Different combination of rules and different combination of values inside the rules assumed the great number of different results. I had to create schemes and tables to make the process of testing more organized and vivid.
I applied al the levels of testing ( Smoke, Critical path, Extended) and I have practical experience in all those items on production projects.
Additional theoretical and practical knowledge was gained while attending CDP lectures and performing tasks:
- Regression testing (practiced in regression scope definition, regression strategy design);
- Exploratory testing (studied approaches and how they can be applied to applications under responsibility);
- Functional and Domain testing (checklist creation using functional and domain testing, applying domain testing approach to standard fields);
- Risk-based testing (designed tests using the approach, created risk analysis matrix for one of applications);
- All-pairs testing (used the approach for testing application under responsibility with the help of Pict);
- Scenario-based testing (created soap-opera for the application under responsibility and perform testing according to it, mark - 4.5);
On the latest three projects I worked in the team of developers without any control and I hope I get on very well.
As a part of project activities create TCs having levels as: Smoke, Critical path, Extended.
Able to design test cases of high level of complexity which use logs, DB sql queries, performance test, requre complex data preparation.