Pretty Old saying yet influences Software Development Process

-
Prevention is Better than Cure
An Old medicine in a New bottle
Felt like sharing few lines from a book "Software Testing with Visual Studio by Jeff Levinson" which i came across while reading it, which went in sync with my thoughts which cab be implemented as best approach to cut down the no of the bugs in any Software development process before releasing it to Testing team.
"Developers need to produce code with fewer defects (contrary to popular belief, bugs in functionality are not the sole province of the developer; they are usually nurtured in the requirements phase) and testers need to provide better information to developers to help them run down bugs in the application" lines quoted from the book. 

My concise was that more Bugs detected were not because the Developers lack good coding skills but due to the case that requirements were not pretty much transparent or due to lack of visibility on how the final outcome of the feature to be implemented should look like. Where some part of this can possible be overcome upfront by collaboration with QA & BA teams).

with experience of working & having an eye on applications built on top of various platforms, technologies & tests conducted, testers will have mindset of how an application should look like, should & shouldn't respond to an input from the end user. So with all these inputs gathered from the testing team upfront, feasible cases picked up by Dev team & incorporated would allow the product to be delivered in time & gives a scope for features committed to be Done without sprint spillover.

Solutions given by Jeff Levinson to the above quoted problem in his book 

1. Part of this is solved simply by testers having access (at least in a read-only mode) to what the developers are doing. Testers can see the documents the developers are working off of and can trace the requirements to the code.

2. Another part of the solution is that as testers write Test Cases, developers have access to the Test Cases, so they can run them before they submit code for testing.

Its the same old saying "Prevention is Better than Cure" which can be applied to Software development process.

Healthy & collaborative discussion to get an upfront generalized view which is agreed upon by the teams involved on how the system should look like, should & should not behave would save sufficient amount of time which is used for Bug fixing, merging the code, deploying, re-testing & again some other functionality breakage.

Comments

Post a Comment

Popular posts from this blog

QA's approach 2 Java - Understanding Static context

-
Image
            Static Members Flow Class members In java application we are defining objects for communication.Every Object is represented as a model(class). Hence, java application is the combination of classes. And every class in java application is allowed to define following members. 1) static members 2) non-static members Static members flow using JVM architecture : Java class supports definition of 4 static members. 1) static main method 2) static block 3) static variable 4) static method Static main method Example class Demo { //empty..... } How to Compile & Execute a simple Java program? 1) Save the program in "d-drive" with name Demo.java 2) Open command prompt, navigate to the path where the java program is stored 3) Compilation: cmd/> javac Demo.java Demo.class file will be generated. 4) Execution:  cmd/>java Demo Error : main method not found... main method : 1) It is static method, hence...
Read more

Selenium 4 absolute beginners - How to create Batch execution file

-
Sample Batch Execution file @echo off :: Delete the existing log file ERASE C:\Softwares\Workspace\ProductNameAutomation\build.log :: Create a new Empty log file  echo.>C:\Softwares\Workspace\ProductNameAutomation\build.log :: Setting project Home Path SET PROJECT_HOME=C:\Softwares\Workspace\ProductNameAutomation cd %PROJECT_HOME% echo CURRENTLY WORKING ON DIRECTORY %PROJECT_HOME% PATH echo Setting configurations SET M2_HOME=C:\Softwares\Workspace\apache-maven-3.5.4 SET M2=%M2_Home%\bin SET path=%M2_Home%\bin ::SET Java_Home="C:\Program Files (x86)\Java\jdk1.8.0_181" ::Start the test case echo test execution in progress call mvn -f C:\Softwares\Workspace\ProductNameAutomation\pom.xml clean install compile test -X -l C:\Softwares\Workspace\ProductNameAutomation\build.log echo test execution in completed :: Generating report based on above ran test cases echo Report generation is in progress call mvn surefire-report:rep...
Read more

Technologies - Log4J - Create Log4j Configuration File - Where ? How ? What ?

-
  Typical Steps involved in Creating Log4j Configuration file Configure the root logger - What to Log - info/debug/error/fatal messages Configure individual loggers (if needed). Specify appenders -- Where to Log -- in File/Console, etc Specify message layout/Pattern -- How to Log - format to log the message Configuring a Layout PatternLayout lets you determine how data is extracted from log events and formatted for output based on a conversion pattern. Conversion patterns act as placeholders for data that appears in each log event.  For example, let’s break down a PatternLayout commonly used in Log4j: <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/> %d{HH:mm:ss.SSS} formats the date in terms of hours, minutes, seconds, and milliseconds. %t displays the Logger’s current thread. %level displays the severity of the log event. %logger displays the name of the Logger. %m displays the event’s message. Finally, %n adds a new line for the next e...
Read more