Geek Answers Handbook

How can I get the QA team that is more involved in the SDLC?

I worked in environments in which the QA team was actively involved in the development process from the very beginning of the project through service. As a rule, I consider this to be effective, since the QA team has an idea of ​​what is happening from a business perspective at an early stage of the process. They can start work on test cases very early.

However, I also worked in environments where the QA team was very unconnected with the development team. They are not interested in this process and simply participate in the completion of the development phase, are scrambled to come up with tests, and then perform a limited set of tests based on their own understanding of business requirements.

What are your feelings for this? What do you think the QA team should be in the process? How can you translate a team that is used to being “uninvolved” to those who are actively involved in this process?

+5
source share
8 answers

I welcome your goal to get the QA / Test involved in the process earlier. I am a big supporter of having a strong testing team, involved from the very beginning of the process to the end. Nice to see that development will include QA. Too often, they are resistant to participation in testing.

, QA , . , , . QA , ( , ). . , -, .

QA, . QA. , , , , , . . . , . , , . , . , , , .

, QA, , . , .

, - -. , . .

+4

, qa , .

, , - . , ( ) .

QA, , , , .

, , , .

+1

, QA . , . , , , . , . . QA - , . , .

+1

, . , , , QA "". , QA Dev ( !), . , , Development, .

, . , .

QA, . , . , , .

, , , QA , . .

+1

. , QA , , - . QA , , , .

, " :"

  • .
  • . -, .
  • , .
  • .
  • , "".
  • .
  • , /.
  • .
  • .
  • .
  • .
  • .

: ,

  • .
  • .
  • .
  • , .
  • .
  • .
  • , .
  • , .
  • , , .

, , , , , , ?

+1

? , QA ( ), ( ) .

, , , (ology) , (, RUP XP). QA , , , , , , , .

0

QA , , .

, , , ; , QA: -, . , , , : , , , .

QA, /: , .

0

QA, , () , - . , Software QA . QA , , .

QA SDLC, , (\ ), .

QA should also run these tests against the existing code base. This confirms that the test wiring is working correctly and that new tests do not fail by mistake without requiring any new code. Obviously, new tests should also fail for the expected reason. This tests the tests themselves, negatively: it excludes the possibility that new tests will always pass, and therefore are useless. Good, so that day one and two.

0
source

More articles:


All Articles