Intern Final Qa Project On Intership
Intern Final Qa Project On Intership
Intern Final Qa Project On Intership
PURBANCHAL UNIVERSITY
College of Information Technology and Engineering
PU Registration Number: 024-3-2-00759-2015
An
Internship Report On
Quality Assurance
At
Broadway Infosys
Submitted by:
Santosh Adhikari
Symbol No. 371911
Date: 28 Jun 201
DECLARATION
I hereby declare that the presented internship report entitled <Quality Assurance= is
uniquely prepared and submitted to Office of Dean, Faculty of Science and
Technology, Purbanchal University is my original work done in the form of partial
fulfillment of requirements for the bachelor of Computer Application (BCA) under
the supervision of Mr. Chandra Bilash Bhurtel. The report is only prepared for my
academic requirement not for any other purpose. It may not be used with the interest
of opposite party of the corporation.
…………………
Santosh Adhikari
ACKNOWLEDGEMENT
The completion of this training work could have been possible with continued and
dedicated effort and guidance of large number of faculty and staff member of the
institute. I acknowledge gratitude to all of them. I wish to acknowledge my deep
gratitude to Mr. Abhinit Karn senior QA at Broadway Infosys for his cooperation and
guidance.
I am also thankful to his lab assistant that provided staunch support throughout this
training and helped me to complete training successfully. I feel great privilege to
express sincere gratitude to Mr. Chandra Bilas Bhurtel, Vice Principle at CITE and
Mr. Bhanu Niraula, The Head of Department, Science and Technology, CITE whose
guidance, constant supervision, valuable suggestions and selfless assistance have
proved to be more than helpful in the field and completion of this internship result
with excellent result.
Santosh Adhikari
ii
ABSTRACT
This internship report contains the details of the activities carried out during the
internship conducted at Broadway Infosys. It was a real time work experience. I had
chance to learn about the different Quality Assurance tools and technology. I was able
to gather a lot of knowledge and experience from my mentor and other professionals.
It also taught us how to work in a group and be an efficient team member.
iii
TABLE OF CONTENT
DECLARATION............................................................................................................i
ACKNOWLEDGEMENT.............................................................................................ii
ABSTRACT.................................................................................................................iii
LIST OF FIGURES......................................................................................................iv
LIST OF TABLES.........................................................................................................v
ABBREVIATIONS......................................................................................................vi
CHAPTER 1: INTRODUCTION..................................................................................1
1.3.1 Introduction...................................................................................................2
1.4.1 Placement......................................................................................................3
1.6 Motivation............................................................................................................6
2.1 Introduction..........................................................................................................7
2.5.2 Jira...............................................................................................................11
2.5.3 Mantis.........................................................................................................14
2.5.4 JMeter.........................................................................................................14
3.1 Conclusion.........................................................................................................20
REFERENCE..............................................................................................................21
LIST OF FIGURES
iv
LIST OF TABLES
ABBREVIATIONS
ASP
Active Server Page
BCA
Bachelor of Computer Application
CITE
College of Information Technology and Engineering
CSS
Cascading Style Sheet
HTML
Hypertext Markup Language
PDCA
Plan Do Check Act
PHP
Hypertext Preprocessor
PU
Purbanchal University
QA
Quality Assurance
QTP
Quick Test Professional
SDLC
Software Development Life Cycle
SQ
Software Quality
SQL
Structured Query Language
UFT
Unified Functional Testing
vi
CHAPTER 1: INTRODUCTION
1.3.1 Introduction
Broadway Infosys ensures that learners is imparted with the highest quality in the
Courses they undertake. To meet the international standards in terms of IT education
and its application, they incorporate an efficient teaching methodology. It facilitate
trainees with a well-equipped lab environment and a perfect learning ambience where
they can work, learn and grow. Also, to keep the pace of the dynamic IT field, the
course curriculum is revised and updated at frequent intervals.
The Training is also designed to fulfill the requirements for internship programs for
semester students who wish to do Training, a mandatory part of their curriculum.
Students who wish to upgrade their existing skills can also undergo the program.
Students wanting to do International Certifications should do this program.
1.4.1 Placement
During the period of internship. The internee was placed in one of the Department of
Broadway Infosys. Internee also got an opportunity to learn about some of the latest
automation tools.
As an internee of QA, they have guide internee for testing and finding bugs of web
application which is developed using PHP Laravel framework. Laravel is simply a
PHP framework which provides a better development environment for web
applications. It can be used to build only web applications.
The required duration of internship for BCA affiliated to PU, demands the time span
of eight weeks. So the internee worked for following time frame.
Plan
Act
Do
Check
These above steps are repeated to ensure that processes followed in the organization
are evaluated and improved on a periodic basis. Let's look into the above steps in
detail:
Plan - Organization should plan and establish the process related objectives
and determine the processes that are required to deliver a high-Quality end
product.
Do - Development and testing of Processes and also "do" changes in the
processes.
Check - Monitoring of processes, modify the processes, and check whether it
meets the predetermined objectives.
Act - Implement actions that are necessary to achieve improvements in the
processes.
An organization must use Quality Assurance to ensure that the product is designed
and implemented with correct procedures. This helps reduce problems and errors, in
the final product.
1.6 Motivation
As it is one of the reputable institutions, at first, the internee came to know about it
through internet and CAN Infotech. But later after meeting and consulting with the
representative, the internee became familiar with their vision and objectives. They
provide favorable environment for the trainees by providing instructors and advising
with proper guidelines whenever necessary.
As an intern, the internee’s responsibilities at Broadway Infosys was to cover the test
as per the requirement and as assigned. For this it required knowledge and skills about
various SDLC and understanding of test principles, testing types like black box
testing & white box testing, error reporting, bug finding, use of automation tools and
use of SQL etc. and general knowledge of programming languages like PHP, C, C++,
JAVA, CSS etc. The main responsibility was to ensure that the web application
developed or any application/software developed must be bug free, meet the quality
standards and most importantly meet the expectations of client. While pursuing
internship as QA, it also requires continuous interactions with project managers and
developers too. During my internship period internee mostly worked on a web
application.
6
Downloaded by Manjila Khatiwada ([email protected])
lOMoARcPSD|24664571
2.1 Introduction
Internee’s first day at internship mostly passed by getting basic concept and required
knowledge about QA. The internee made quite detailed notes each day about what he
learned as well as of the tasks he had to do each day throughout the internship. Since
these tasks are mostly project related, he can’t disclose these though so daily
reporting isn’t possible.
The internee’s 1st day at internship was at 5th march 2019, which was Tuesday. He got
in at 10:00 am as was instructed to me by mail. He was given a quick tour of the
company and shown the place where from where he had to work. There were few
other internees there as well so shook hands with every internee there and waited for
supervisor to come.
After couple of minutes the supervisor came and we had a 5 minutes introductory
session. Then he began to explain basic concepts with the starting question, what is
QA? Then he started giving theoretical knowledge about QA till 1PM. From1PM
to1:30 PM lunch break was provided. After lunch break again it continued till 5PM.
This process continued for about 7 days where many topics like SDLC and brief
concept of SQ was also given. The internee was given detailed theoretical information
at a rapid pace during these 7 days.
are building the product right i.e., to verify the requirements which we have and to
verify whether we are developing the product accordingly or not.
Black box testing, also known as behavioral testing, is a software testing method in
which the internal structure/design/implementation of the item being tested is not
known to the tester. These tests can be functional or non-functional, though usually
functional. This method is named so because the software program, in the eyes of the
tester, is like a black box; inside which one cannot see. This method attempts to find
errors in the following categories:
White box testing (also known as Clear Box Testing, Open Box Testing, Glass Box
Testing, Transparent Box Testing, Code-Based Testing or Structural Testing) is
This method is named so because the software program, in the eyes of the tester, is
like a white/transparent box; inside which one clearly sees.
Manual testing is the process of testing the software manually to find the defects.
Tester should have the perspective of end users and to ensure all the features are
working as mentioned in the requirement document. In this process, testers execute
the test cases and generate the reports manually without using any automation tools.
Here in Broadway test cases were written using MS-excel for manual testing. The
practice of writing test cases in Excel gave me chance to make a logical table for
calculations as well as for testing various outcomes were calculated according to
input and were displaying correct output or not. In general I covered with this
following topics to write manual test cases.
Test case ID
Test title
Test summary
Pre conditions
Test Priority
Test steps
Test data
Expected Result
Actual result
Status
Automation testing is the process of testing the software using an automation tool to
find the defects. In this process, testers execute the test scripts and generate the test
results automatically by using automation tools. Some of the famous automation
testing tools for functional testing are QTP/UFT and Selenium. Automated software
testing's main benefit is that it simplifies as much manual effort as possible. If unit
testing consumes a large percentage of a QA team's resources, for example, then this
process should be evaluated as a candidate for automation. Automated testing tools
execute tests, report outcomes and compare results with earlier test runs. Automated
tests can run repeatedly at any time of day. This approach fits in with continuous
testing, software development practices.
10
During my internship period I got opportunity to learn about some automated testing
tools which I have described as following:
2.5.2 Jira
Jira is a highly popular tool used by QA teams for tracking bugs, new feature
requests, and tasks. Its customizable nature allows for a broad set of use cases when it
comes to managing software development projects. Jira is great for managing high
volume backlogs and for bringing teams together to focus on the work that matters.
The most common way software testing teams use Jira is to log bugs and new
features.
Jira can also be used as a test case management tool, but because Jira has not been
specifically designed for this role, a number of time-intensive configurations need to
be made to make it operable. For this reason, an increasing number of users are
choosing to integrate Jira with a reliable, purpose-built test case management tool,
such as TestLodge. The integration gives them access to the twin resources, letting
them get on with the actual job of testing far quicker than by using Jira alone. Some
specific features of Jira that are useful for Test Case Management:
11
Downloaded by Manjila Khatiwada ([email protected])
lOMoARcPSD|24664571
After running test cases written on excel, bugs used to be detected. These bugs were
recorded by creating token at Jira and were used to be assigned to the developers to
solve using Jira. While emailing bugs to the developers or walking up to a developer
can be useful, but with such a large team it can hamper workflow and slow the pace
of work. To reduce this, bugs status is recorded in Jira, a project management
software which can be accessed in a browser. Jira allows a developer to create a new
entry for each bug and provide detailed information to reproduce the bug. In addition,
bugs can be given relations to other bugs and priorities for fixing. Bugs are either
open, resolved (fixed but require validation), fixed in next release or closed. They are
reported in different categories, which can be filtered.
Bugs
Resolved (bugs supposedly fixed, require validation before closing)
Fixed in next release (not fixed in current version but in next version of editor)
While using Jira for reporting bugs, first knowing bug life cycle is must. Bug life
cycle is the process of creating ticket, assigning to the developer, fixing the bug and
closing the ticket.
12
The following figure shows the bug life cycle step by step
13
2.5.3 Mantis
ANTIS is an open source bug tracking software. It can be used to track bug for
various software projects. We can easily download and install the Mantis for our
use. Mantis bug tracker now also provides a hosted version of the software.
2.5.4 JMeter
The Apache JMeterTM is pure Java open source software, which was first developed
by Stefano Mazzocchi of the Apache Software Foundation, designed to load test
functional behavior and measure performance. You can use JMeter to analyze and
measure the performance of web application or a variety of services. Performance
Testing means testing a web application against heavy load, multiple and concurrent
user traffic. JMeter originally is used for testing Web Application or FTP application.
Nowadays, it is used for a functional test, database server test etc.
Advantages of JMeter
Open source license: JMeter is totally free, allows developer use the source
code for the development
14
Friendly GUI: JMeter is extremely easy to use and doesn't take time to get
familiar with it.
Platform independent: JMeter is 100% pure Java desktop application. So it
can run on multiple platforms.
Full multithreading framework. JMeter allows concurrent and simultaneous
sampling of different functions by a separate thread group.
Visualize Test Result: Test result can be displayed in a different format such
as chart, table, tree and log file.
Easy installation: You just copy and run the *.bat file to run JMeter. No
installation needed.
Highly Extensible: You can write your own tests. JMeter also supports
visualization plugins allow you to extend your testing.
Multiple testing strategy: JMeter supports many testing strategies such as
Load Testing, Distributed Testing, and Functional Testing.
Simulation: JMeter can simulate multiple users with concurrent threads, create
a heavy load against web application under test.
15
16
QTP/UFT allows tester to test both web pages and websites as well as desktop
application (both online and offline). Here we can run and test any application either
by writing codes manually or by using record button, going to desire application and
giving the test input, stopping record button and making the code by adding attributes
and giving a set of conditions to check.
17
Selenium is a free (open source) automated testing suite for web applications across
different browsers and platforms. It is quite similar to QTP/UFT but difference is only
that Selenium focuses on automating web-based applications. Testing done using
Selenium tool is usually referred as Selenium Testing.
Selenium also allows record and play button like QTP/UFT but it didn’t support
complex locators like XPath and link name. Thus, selenium Remote control and
WebDriver fused and created Selenium 2 which later got improved and became
Selenium 3.
Selenium allows tester to create a test code for each component such as dropdown,
button or text field and provide detailed testing to find the bug. It uses different
functions such as find.Element and select.Element to find the exact component to test
and select the exact component to test.
18
After running test cases written on excel, bugs used to be detected. These bugs were
recorded by creating token at Jira and were used to be assigned to the developers to
solve using Jira. While emailing bugs to the developers or walking up to a developer
can be useful, but with such a large team it can hamper workflow and slow the pace
of work. To reduce this, bugs status is recorded in Jira, a project management
software which can be accessed in a browser.
Jira allows a developer to create a new entry for each bug and provide detailed
information to reproduce the bug. In addition, bugs can be given relations to other
bugs and priorities for fixing. Bugs are either open, resolved (fixed but require
validation), fixed in next release or closed. They are reported in different categories,
which can be filtered.
1. Bugs
2. Resolved (bugs supposedly fixed, require validation before closing)
3. Fixed in next release (not fixed in current version but in next version of editor)
While using Jira for reporting bugs, first knowing bug life cycle is must. Bug life
cycle is the process of creating ticket, assigning to the developer, fixing the bug and
closing the ticket.
19
3.1 Conclusion
The Internship period at Broadway Infosys has been very productive and helpful.
There is a big difference in the PU academic course and the tasks and activities
during the actual work. In college we learn how quality is important and some basic
quality software benefits and features, where during internship, it is learnt far more
than the basics. Alongside of manual test case writing, various automation tools use
and how to tackle and report bug in reality is learnt.
Lastly, the internship was a wonderful experience in the exposure to the professional
field. The internee learned so much from there and it helped him to grow by many
folds. This internship showed one thing that the college course is so old fashioned and
outdated and has to be updated. In near future if opportunity is provided, the internee
surely would love to be a QA specialist in Broadway Infosys to pay how it helped in
the internship.
Working at Broadway Infosys provides the internee with the following aspects:
20
REFERENCE
21