Луиза красивая и статная женщина, приятно смотреть на вас. Вы оба как профессиональные ведущие!

Оззи хороший преподаватель и интересный рассказчик. Тот человек которого можно заслушаться: чистая, грамотная речь.

Ozzy топ teacher!

❤❤❤

А где канал Портнов блог?

Потому что он портнов компьютер скул

Так канал с которого вы говорите Портнов компьютер скул а не блог

Круто!

Вот так сейчас людей рекрутируют в профессию 😢

He is the legend! 🦾

Молоденький, классный😍

Классное видео. 👍❤

Who is SLAVA skrabin? Is he teacher?

Спасибо❤👌

Потом делайте автоматизацию.

Как же муж отпустил вас в дальнобой!? Это же опасно, долгие дороги в пути😬 Рада, что выпошли к Михаилу учиться👍

Добрый день!!!!! Я подписчик Михаила!!!!❤👍 Спасибо команде Михаила!!!❤👍 Вы профессионалы!!!!👍

Учусь на курсе сейчас очень много слышу о том что помогают найти работу это самое важное после окончания курса

Спасибо большое за такую возможность. Очень хотелось бы присоединиться к вам.

сейчас никого не нанимают, особенно новичков после курсов, если у вас есть опыт то да возможности думаю будут, а entry positions почти нет либо хотят и там чтобы был опыт уже, сами загуглите

Nice woman, nice story :) Wish success!

Спасибо! Очень интересная история :)

Очень интересно что дальше! Обязательно делитесь

Тоже учусь у Михаила. Желаю вам успехов и удачи!

Спасибо за видео.

Thank you so much! Iana, you have amazing teaching skills and a huge amount of knowledge! Even after 11 years, I found that all the information you shared is still actual and very helpful!

Hello, good news! Can former students attend such interships?

Благодарю

❤

❤️

❤

Вувувуву

супер-лекция

Дай Бог вам долгих лет жизни София, к концу видео прослезился аж, спасибо за такую возможность обучения. Луиза и вам спасибо за информацию. Осталось только выграть в лотерею.

А кто резидент других штатов, есть такие программы?

Информация - 🔥 огонь 🔥

София просто прелестна.

❤️🙏

Спасибо огромное ! ❤

Is it online?

Приедем обязательно ❤❤❤

Спасибо команде Михаила. Очень полезная информация.👍

Поздравляю вашу школу с серьезным юбюлеем. Пригласите канал Silicon pravda

00:00 *Check-out* is a process of taking a file out (extracting) from a system. When you check-out any file it is logged with your name and only you may change it. After the change is done, *Unit Test* is performed - then you integrate the file back into the system. This is a *Check-In* process. Every Check-out - Check-In cycle adds a 1 to version number. Versioning is running individually for every file. The purpose of this approach is to make sure that developers do not step on the other terms. That allows people to work eventually on the files. 04:28 M.Portnov: QA should point build # in a bug report to avoid misunderstanding with the developers 05:40 Now back to our Test Cases (but really started the discussion about "who assigns *Priority* in the bug report" ) 07:15 Now let's have a look at the timeline for our project. When you are doing the first test cycle, every day different managers will ask you: "Are we ready to release?" How can you prove that a Product is not ready to be released? -- TCs are very handy for this purpose (8:48) 08:50 *Execution Rate (ER)* is the number of TCs executed divided by the number of TCs total. The QA Team monitors it daily. The goal of the QA Team is to reach 100% of ER by the end of the testing cycle. 11:12 In addition to ER there exists the *Pass Rate (PR)* which is the number of TCs passed divided by the number of TCs total (or executed). The Pass Rate is very important: it shows you what is the Quality of the Product when you execute some (or total) number of TCs. So, *it quantitates the Quality* by using the number of TCs. 13:00 Iana describes the typical situation with the ER and PR during several Testing Cycles and 15:00 Iana explains possible risks at the 2nd cycle with *particular figures (ER 60% and PR 20%)* . No need to wait until the end of the cycle if you see a negative trend by the middle of the cycle. QA should raise a red flag and investigate the Root Cause of the trend 16:50 *Other possible figures (ER 60% and PR 70%)* show a positive trend - it's Ok. We are still not ready to release, but the trend is good :) 17:40 You can (should) go to the (next) cycle until you reach the targeted Quality Level, which depends on a particular project, a particular company. Usually, the ER is targeted at (95-100)% with PR at (90-95-100)% 18:30 there is a typical INTERVIEW QUESTION: "How would you determine the time to stop testing?" - in this case, you may come up with some numbers, not by saying "When the Quality is not increased with continuing testing" 20:00 When you make the decision regarding stopping testing, you should not take into account only these criteria (ER/PR). As well, you have to be sure that bugs that are still out of scope - that they are not critical

6:00 Describing of the *Compilation* process and the *Build* term. After compilation is done, a build contains some Bugs (all logical ones, maybe some synthacsis ones...). And this build comes to QA for testing 9:25 *If you don't have any TCs, you do Exploratory Testing* (aka Alfa Testing) and find bugs randomly (you "shot in the dark"). The purpose of TCs is to find bugs in an organized, systematic, and trackable manner and catch as many bugs as we can 12:35 What do you do, if *you find a bug* (mismatch in SW behavior)? -- first of all, *reproduce it* (do Repro). We do Repro to be sure that it is that TC instructions (not something else) that resulted in the bug. Otherwise, we should remember our steps and document them in the other TC in our bug tracking system. I recommend doing it, even if we can not reproduce the bug right now (due to the bug could be a result of randomly occurring reasons), and attach a log file with this error. 16:03 M.Portnov explains understanding of 'Test Case' term in the IT Industry. 18:35 Iana asks again: "Let's you are sure that after executing of TC instructions you actually see the NOT expected result. *What do you do next?* " - and then explains her answer: discuss the issue with colleagues, check it in actual documentation, and after that make a decision about documenting a bug report in the bug tracking system. 24:00 What is going on after developers fixed bugs in the build_#1 ? 25:55 *Bug Injection Rate* - number of new bugs created during fixing discovered 10 bugs (in %). It is about (25-30) % according to Iana.

*promosm* 😉

Благодарю вас за информацию . 🎉❤

Имел честь побывать на тренинге Яна, когда он работал у нас в компании в России. Было круто! Рад увидеть знакомое лицо на канале 😊