Testing Process Quick Refresh

-


                         Testing Process High level walk through

Testing Process starts after the ‘Build’ is released to the Testing Team, Before to that the Development Team will do ‘Smoke Testing’. Once the Build is released to the Testing team, Then First they will conduct

‘Build Acceptance Testing’ (Once, the build is released to the Testing Team, then whatever the Testing Team will do is nothing but BAT)

Re & Regression Testing (Conducted Testing on the same functionality again & again with multiple sets of data, To check whether it is working fine or not).

Static Testing (Conducted Testing on the application or its related factors without doing any actions, nothing but GUI Testing, Doc.Testing, Code reviews......etc.)

Dynamic Testing (Conducted Testing on the application or its related factors by performing some actions, nothing but Functionality Testing)


Compatibility Testing (To check whether the application is suitable with different environments or not)

Usability Testing (To check the User-friendliness of the application)

Monkey Testing (To check the Stability of the application by using abnormal actions on the application)

Soak Testing (Reliability Testing) (To check whether the application is Stable or not for a long Period of Time).

Port Testing (It will be done in the Clients Environment, User-desired areas, checking the compatibility, will be done at the Time of Delivery and Maintenance).

End-to-End Testing (It will be performed by the Tester on the End-to-End Scenarios of the Application). It is a very Important kind of Testing in the Company.

Mutation Testing (To Perform Testing on the application or its related factors after doing some changes to them).

Adhoc Testing (The Testers will perform testing in their own style after understanding the requirements very clearly).

Testing Model/Methodology

To deliver a Complete Quality Product to the Client or Customer, there should be one Process Model and Best Model which gives better Output to the Company
·         Waterfall Model
·         Prototyping Model
·         Evolutionary Model
·         Spiral Model
·         Fish Model
·         V-Model


Software Testing Life Cycle (STLC)

Software Testing Life cycle contains 6 phases, they are:
  1.    Test Planning (Test Plan Document will be prepared by Test Lead)
  2.    Test Development
  3.    Test Execution
  4.     Result Analysis
  5.     Bug Tracking
  6.     Reporting

 Test Plan 

is nothing but a Strategic document which contains some information that describes, How to Perform Testing in an Effective, Efficient and in an Optimised (Process of utilising available Resources to their level best and getting maximum possible output) way.

Test Lead/Test Manager will prepare the Test Plan Document.

Index/ Contents of Test Plan:
1.0      Introduction
·         Objective
·         Reference Documents
2.0      Coverage of Testing
·         Features to be tested
·         Features not to be tested
3.0      Test Strategy
·      Levels of Testing
·      Types of Testing
·      Test Design Techniques
·      Configuration Management
·       Test Metrics
·       Terminology
·       Automation Plan
·       List of Automated Tools
4.0      Base Criteria
·         Acceptance Criteria
·         Suspension Criteria
5.0      Test Deliverables
6.0      Test Environment
7.0      Resource Planning
8.0      Scheduling
9.0      Staffing & Training
10.0       Risks & Contingencies
11.0       Assumptions
12.0       Approval Information

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

QA's approach 2 Java - Collections Framework & Generics Introduction

-
Image
Why Collections & why is it called a Framework? First Question: Why Collections? Collections are used to overcome problems with variables, arrays, classes like size problem, type problem, non existence of predefined operations/methods, etc. To get a Overview of the above discussed problems, click on this link What is a Framework? Its a semi-finished re-usable application, providing some low level services, which can be customized according to our requirement.  Second Question: Why is it called a Framework? Collection API is available in util package & its called a Framework for the reason that, java programmers were not restricted to just utilize the existing classes making them final but was allowed to expand on top of the exiting classes inheriting them. Collections framework gives a clear example of when to use Interface & abstract class Classification of Collection Framework: In Collection Framework all the classes are classified into 3 cat...
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