1Why is a bug found after release more expensive than one found at the requirements stage?, Because programmers are lazy, Because fixing it requires rework of code, tests, release and may affect users, Because requirements are always wrong, There is no difference, 2What does a unit test check?, The entire product as a whole, How modules work together, One function / method in isolation, Usability of the interface, 3. Which test is the most expensive and slowest?, Unit, Integration, E2E (end-to-end), All are the same, 4 What does the Red → Green → Refactor cycle in TDD mean?*, A traffic light on the road, Failing test → code that passes the test → code improvement, Three levels of testing, Three colors of the interface, 5. Why is regression testing needed?, - B) To make sure that new changes didn't break the old functionality, - A) To find new bugs in a new feature, To speed up the application, To reduce code size, 6 Who is responsible for product quality?*, Only QA engineer, Only Team Lead, Only the customer, The whole team, 7 Which of these is non-functional testing?, Checking the "Buy" button, Checking page load speed, Checking account login, Checking discount calculation, 8 Why is "covering everything with E2E tests" a bad idea?, They don't check anything, They are slow, expensive and fragile, They cannot be automated, They don't find bugs, 9 What can happen without security testing?, Nothing, security is not important, Data leaks, hacks, fines, The application will become faster, The code will become shorter, 10 The main idea of today's lesson:, Testing is needed to punish developers, Only QA writes tests, You only need to test before release, Testing is about confidence that the product works

Why Testing is Important in Software Development

by
Print
Embed

Leaderboard

Visual style

Options

Switch template

Continue editing: ?