Tester's Musings

If i was assigned to multiple projects as a software tester (and the only tester) i should NOT succumb to pressure and 'juggle.' Each one has its own release date, and the PMs must decide which one takes priority release, which in turn dictates which one takes priority testing. { Testing to a specific degree of product acceptability should be agreed first; then the rate/speed of testing follows the degree of acceptability; subject to the release dates of improvements and fixes; which in turn is subject to the complexity of the feature/s being developed } cross this with { N projects } and we see that the 'quality' of the product/s is more related to the 'degree of acceptability' and is never derived from 'juggling between projects.' source

  i have found out that after a while -- where the tester has proven his mettle by his documentation, artefacts, and proven investigative and evaluative capabilities -- more often than not, respect grows between Dev and Tester. Devs start to not dismiss our bug report anymore -- they say 'it works on my machine, so i must be missing something; can you show me?' https://www.linkedin.com/feed/update/urn:li:activity:7250131780119224321/