Phone Book Agile Software Testing

This report provides a deeper understanding of black box testing in an agile environment and use of Test software management tool like TestRail. The report also includes evaluation and justification of the testing process.

Running head PHONE BOOK AGILE SOFTWARE TESTING i
Phone Book Agile Software Testing
Author
Institution of Affiliation

PHONE BOOK SOFTWARE TESTING ii
CONTENTS
CONTENTS................................................................................................................................................ii
EXECUTIVE SUMMARY.........................................................................................................................1
LITERATURE REVIEW............................................................................................................................3
Test Plan-For every Iteration...................................................................................................................5
The Agile Testing Activities during an iteration......................................................................................6
Unit Testing.............................................................................................................................................7
Performance testing................................................................................................................................7
EVALUATION AND JUSTIFICATION....................................................................................................8
CONCLUSION.........................................................................................................................................11
REFERENCES..........................................................................................................................................12
ii

PHONE BOOK SOFTWARE TESTING 1
EXECUTIVE SUMMARY
This report has been written after conducting an intensive software testing on a
phonebook software that was deployed in a cloud service. Our team has compiled a report that
provides a deeper understanding of black box testing in an agile environment and use of Test
software management tool like TestRail.
The phonebook software in subject is open to a number of users and is synchronized with
the user’s phonebook so that information added is synced both in the website and the phonebook.
The user can do a bunch of things in the software, for example they can create an account in the
website, insert multiple sheets to the phonebook, every sheet can include information up to
10000 people, log in to the website using their credentials (username and password), share the
sheet with their friend by using the email of their friend where that email address is used to log
on to the website, provides write access to their friend then the friend can be able to modify any
contact information, import information from a CSV (Comma Separated Values) file and vice
versa. This information is going to be saved to a certain selected sheet, and finally the user can
also export information to a sheet in a CSV file.
We found that there are bugs in every other software including our phonebook software.
Developers encounter bugs and hence testing helps to identify the bugs so that they can be fixed
before being deployed to user. However there are risks of deploying the software in a cloud
service because the benefits from the agility and scalability that cloud services offer, there are
issues of security and privacy of personal data.
1

PHONE BOOK SOFTWARE TESTING 2
For our case, agile testing environment has proved to be a productive and best practice
since testers and developers work together at the same time, testing is not a separate phase and
occurs concurrently with development. However, if these tests to the software would not have
been done, there could be poor results in the deployment process.
2

PHONE BOOK SOFTWARE TESTING 3
LITERATURE REVIEW
Software testing has work in to it. The processes are long but with the aid of testing tools
such as TestRails which is integrated with JIRA, it makes it a lot easier. The other thing to
consider is the environment and the methodology that one uses during testing. For our case, agile
environment proved to be the best since every individual in the team contributes to the testing
and this is efficient.
We used TestRail* to write the test cases and scenarios. The modern software
management tool has the ability to track and save some of these test cases and then automate
them so they can run between iterations. This comes in handy and is a huge boost to agile
methodologies, and also helps ensure functionality under pressure.
Our software testing team used black box testing method to generate independent test
cases of software internal structure. Different approaches and techniques of black box testing are
used to find errors. This type of testing is either direct or indirect to the specification of software
hence it is sometimes known as specification based testing. For our case, we used test case for
the nine scenarios in our software as shown below.
3

PHONE BOOK SOFTWARE TESTING 4
4

PHONE BOOK SOFTWARE TESTING 5
The figure above shows how the black box testing method works. It does not involve the
technical part. The users do not see the internal part of the software. They only input the
requirements and the user gets the desired results and then finally generates the final report.
Having worked in the agile environment, the agile testing activities at project level include
Test Plan-For every Iteration
In the modern software management tool (TestRail) that we used, we created test plans as
shown above in order to add and run results.
- Regression Testing
- Release Activities (Test Related) (Hambling, 2017)
5

PHONE BOOK SOFTWARE TESTING 6
The Agile Testing Activities during an iteration
1. Participating in iteration planning
2. Estimating tasks from the view of testing
3. Writing test cases using the feature descriptions
4. Unit Testing
5. Integration Testing
6. Feature Testing
7. Defect Fixing
8. Integration Testing
9. Acceptance Testing
10. Status Reporting on Progress of Testing
In TestRail management tool, it enhanced our testing of the software because it provides the
run results and reports which includes graphs and charts.
6

PHONE BOOK SOFTWARE TESTING 7
Unit Testing
This is the kind of testing which was done after every module during the coding process of the
program. During unit testing the programmer ensures that upon the completion of every
programming stage, there are no bugs within the program code. The main reason why we did
unit testing was to reduce the time wastage since bugs might get accumulated and will make it
difficult during the real system test
Performance testing
This the kind of testing where the performance of the phonebook software was tested to check
the stress and how the software is going to interact with other applications. The software was
tested on how it can be integrated with others and will make it run without presenting bugs to the
users.
11. Defect Tracking
Agile environment also has principles that are important for team members to have so that
they can be productive and meet the objectives of the team effectively. They should:
 Provide continuous response to concerns.
 Enable effective communication.
 Practice continuous improvement.
 Maintain simple and user friendly interaction.
 Pay attention to change in order to suit the user of the software.
 Be organized and also follow steps provided in order.
 Focus on the users of the system so that they can effectively meet their requirements.
 Give value to the user.
7

PHONE BOOK SOFTWARE TESTING 8
EVALUATION AND JUSTIFICATION
The tester or the user does not require a deeper understanding of the inner working of the
software and only requires some information about its inner functionalities. This is the reason
why black box testing was preferred. Because the software is built to save the name, address and
phone number of users to the app and website, it should be user friendly and take care of security
and privacy of the data. Several test could be performed on the program to check on its
functionality. First, quality assurance must be made of the program. The expectations or the user
requirements should be met without compromise. The feedback from the user will help
determine the usability of the software. The software is integrated with other programs and
should be able to run in different browsers with the same level of responsiveness. The program
should not have problems when in different operating systems.
8

PHONE BOOK SOFTWARE TESTING 9
Using TestRails, we develop integration and acceptance testing using JIRA integration as
below and it was successful.
We also performed stress testing, load testing, volume testing. By adding 9 test cases, test
plans and data for the three types of data for multiple persons which include Name, Phone and
Address. We added results and tested if the software works under stress or volume.
We also added multiple users in the test who can add data, delete data, share data by inviting
their friends and also import and export the information of their choice as shown below
9

PHONE BOOK SOFTWARE TESTING 10
Black box testing using TestRail has proved to be of great assistance during the testing of
the software. It not only helped in checking the performance of the program but helped explore
its functionality too. For future programming, these testing tools are going to be used by my
team. Therefore it is preferable.
10

PHONE BOOK SOFTWARE TESTING 11
CONCLUSION
For one to do an effective software testing, they should be able to choose a tool that is
convenient and modern to aid simulate the testing environment. Agile environment allows a team
to code at the same perform testing. This allows them to fix bugs easily when they arise.
Software testing is a broad area and should be done with a lot of keenness. Web applications are
best tested with the Black box security scanners due to their agility in checking vulnerability in
security in web applications. Its security vulnerabilities must be taken care of to reduce the issue
of security and privacy concerns. Nevertheless, the application must undergo all the testing from
its interface to its compatibility.
11

PHONE BOOK SOFTWARE TESTING 12
REFERENCES
Myers, G. J., Sandler, C., & Badgett, T. (2011). The art of software testing. John Wiley & Sons. Ammann,
P., & Offutt, J. (2016). Introduction to software testing. Cambridge University Press.
Hetzel, W. C., & Hetzel, B. (2010). The complete guide to software testing (pp. 201-202).
Wellesley, MA: QED Information Sciences.
El‐Far, I. K., & Whittaker, J. A. (2012). Model‐based software testing. Encyclopedia of Software
Engineering.
Pohl, K. (2010). Requirements engineering: fundamentals, principles, and techniques. Springer
Publishing Company, Incorporated.
Kormann, B., Tikhonov, D., & Vogel-Heuser, B. (2012). Automated PLC software testing using adapted
UML sequence diagrams. IFAC Proceedings Volumes, 45(6), 1615-1621.
Loveland, S., Miller, G., Prewitt, R., & Shannon, M. (2015). Software Testing Techniques:
Finding the Defects that Matter. New Delhi: Charles River Media.
Egan, J. P. (2015). Articulation testing methods. The Laryngoscope, 58(9), 955-991.
Ward, J., & Daniel, E. (2006). Benefits management: Delivering value from IS & IT investments (p. 418).
Chichester: John Wiley & Sons.
Melamed, K., & Melamed, Y. (2007). U.S. Patent No. 7,313,564. Washington, DC: U.S. Patent and
Trademark Office.
Srivastava, P. R., Singh, A. K., Kumhar, H., & Jain, M. (2012). Optimal test sequence generation in state
based testing using cuckoo search. International Journal of Applied Evolutionary Computation
(IJAEC), 3(3), 17-32.
12

PHONE BOOK SOFTWARE TESTING 13
13