Saturday, 25 January 2014

Questioning - At every stage of SDLC.


As developers or even programmers and testers we are also entitled to question the product at every phase of Software Development Life Cycle(SDLC), starting with collating requirements and even after the product's release.



  • Question the product's reach and usage whenever required.
  • Question the need for adding a new feature and aid removing irrelevant features.

I was watching this video shared by a friend and infer these lessons relevant to testing from it.



Link to the video: 
https://www.youtube.com/watch?v=tfw0KapQ3qw

https://www.youtube.com/watchfeature=player_embedded&v=n_1apYo6-Ow

Do view the video before proceeding.

Observations made with regard to testing (in the context of this video) is summarized below.

Here are a few points to ponder:


1) Question the product under test - Not just in terms of targets met, records broken, performance achieved but also relevant in terms of it's usage, test data and technology used, people benefited and software re-usability.
2) Question the design of the product with regard to it's relevance to current needs.
3) Unit test by programmer and/or test teams post a quick fix.
4) Re-test.
Are we ready to re-test?
Does the existing test plan hold good for re-test?
Does the test environment requires to be fine-tuned for the next run?
Should we re-visit the scope of testing for the purpose of re-testing? 
Shall we re-strategize and then re-test?  
5) Regression test.
Test the new fix and Check if the existing functionality is broken post the fixes made to the product.
6) Perform impact analysis on the quick fixes made so as to not overlook on the overall performance of the product.
7) Test the impacted/affected flows with same/different test data prior to the product's release.
8) Know if the test requires a manual intervention in case of automated test runs. 
9) Stabilize the test environment. An essential aspect which should not be overlooked when comparing results from first test run with the subsequent test runs.

Start questioning. Do instigate the need for questioning and open doors for thoughts and learnings which can save time and effort. And help build better teams and better products.

Related articles:
http://www.createadaptablelife.com/2014/01/ask-for-what-you-want.html
http://www.halasaleh.com/2013/08/ask-questions-get-answers-and-check-out-the-link-at-the-end/

If you have read or encountered articles on the need to question and question at all stages of software development and testing life cycle, do share the links below in the comments section and I shall include them here under the related articles. Thank you.

From around the tweet-verse, Quoting Michael Bolton ‏@michaelbolton
#Testing is NOT about making sure that test cases pass. It's about using ANY means to *find problems* that *harm or annoy* *people*.

A tip: The Short cut key Control+S while you are on WordWeb window plays the sound(pronunciation of the word looked up for on Windows 8 OS).

No comments: