Testers best practices

-


Best approaches\practices to be followed while testing an application:


1. Clear cut understanding of the User Story is pretty much important for further course of action, for which we can always go with 3 simple questions a)Whats the Problem statement? Is it going to replace/enhance any existing feature/its a completely new feature b)Whats are suggested solutions & why this is chosen? c)Whats the impact of this feature?

3. Suggest changes when & where necessary, which is the primary role of the QA professional. Since QA person gains a vast experience by working on various platforms, technologies & End to End application functional flows which allows him to gain a very broad view.

For a simple example a QA can suggest displaying a "Successfully uploaded" message instead of displaying the uploaded image itself on the screen. Since this saves some space on the Frame/page which can be used at a later point of time for implementing some new functionality.

3. Turn on the Debug mode in Log4j/Log4.Net, while you begin to start installation/testing, since in general, logging mode will be set to Info. So we will not be able to identify some issues at the early stages.

OR

3. Turn on Debug mode & configure the SMTP address & list of mail id's, the mail to be routed as soon an exception is raised instead of logging it to a file/console. So that as soon as an exception is raised, it will trigger a mail to Developer & QA group. So that no Exception is never missed out without being analyzed & fixed.

One simple example to understand the best approach -
Most mobile app development orgs uses Crash analysis tools, like Crashlytics from google for their application crash analysis.
The app which were install it from playstore & we use it. But at times do to unknown reasons application might crash & we never provide the feedback, but they capture these crashes analyze them & they fix them immediately, as in crashlytics they could get very clear idea of the code which led to application crash. 

4. Continuous discussion about the functionality/Product you were working on with colleagues gives a better approach  to improve & enhance, so that you keep getting more idea's on how best we can improvise, which always leads a way to Quality release.













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