Automation link checker testing with continuous integration


  • Joe Erik Carla Wijaya Bina Nusantara University
  • Abba Suganda Girsang Bina Nusantara University





Automation Testing, Testing, Link Checker, Continuous Integration, Jenkins.


Many links from websites are damaged due to the development of an increasingly large and complex website features. To ensure that no links are broken there is a need for a link checker testing application. But manual testing requires a lot of resources, expensive cost, and takes a long time to check the whole deployment must be done every day, so in this study the manufacture of link checker testing application will run automatically and integrated with Jenkins. With this application, developers can fix broken links in the development stage before being consumed by the public. Automation link checker testing application is using Jenkins as continuous integration tools, Shell Script, PHP Unit framework and PHP programming language will check all the links in the website automatically and report from the test results. Once compared with manual link checking, the test automation application of this link checker is more accurate and faster than checking links manually.





[1] R. S. Pressman, “Software Engineering A Practitioner's Approach (8th Ed.)â€, New York: McGraw Hil, 2014.

[2] M. S. Hossain and M. S. Hosain, "Web Test Integration and Performance Evaluation of E-Commerce Web Sites," International Journal of Computer Science and Information Security, Vol. 10, No. 9, pp. 65-69, 2012.

[3] G. Tassey, “The economic impacts of inadequate infrastructure for software testing.†National Institute of Standards and Technology. Planning Report 02-3, 2002.

[4] S. Singla and H. Kaur, "Selenium Keyword Driven Automation Testing Framework," International Journal of Advanced Research in Computer Science and Software Engineering, Volume 4, Issue 6, pp. 125-129, 2014.

[5] S. Kaur, “An Automated Tool for Web Site Evaluationâ€, International Journal of Computer Science and Information Technologies, Vol. 3(3), pp. 55-69, 2012.

[6] M. Hilton, T. Tunnell, K. Huang, D. Marinov and D. Dig, "Usage, Costs, and Benefits of Continuous Integration in Open-Source Projects," Automated Software Engineering, 2016.

[7] M. Hilton, N. Nelson, and D. Dig, T. Tunnell and D. Marinov, "Continuous Integration (CI) Needs and Wishes for Developers of Proprietary Code," Corvallis, OR: Oregon State University, Dept. of Computer Science, 2016.

[8] B. Vasilescu, Y. Yu, H. Wang, P. Devanbu and V. Filkov, "Quality and productivity outcomes relating to continuous integration in GitHub," Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering, pp. 805-816, 2015.

[9] P. Gerrard. “Risk-based e-business testing. Part 1: Risks and test strategyâ€., 2000.

[10] N. K. Tyagi, A. K. Solanki and M. Wadhwa, "Analysis of Server Log by Web Usage Mining for Website Improvement," International Journal of Computer Science Issues, Vol. 7, Issue 4, pp. 17-21, 2010.

[11] D. J. F. Tawfeq, D. A. M. S. Rahma and E. Q. Ahmed, "Detecting a Broken Link in a Web Site," Al-Mansour Journal Issue, 2012.

[12] V. Kumar, "Comparison of Manual and Automation testing," International Journal of Research in Science and Technology, Vol. No. one, Issue No. V, 2012.

[13] R. M. Sharma, "Quantitative Analysis of Automation and Manual Testing," International Journal of Engineering and Innovative Technology, Volume 4, Issue 1, 2014.

[14] P. M. Duvall, S. Matyas and A. Glover, “Continuous Integration: Improving Software Quality and Reducing Riskâ€, Massachusetts: Pearson Education, Inc., 2007.

[15] R. M. Betz and R. C. Walker, "Implementing Continuous Integration Software in an Established Computational Chemistry Software," Software Engineering for Computational Science and Engineering (SE-CSE), pp. 68-74, 2013.

[16] J. Gray, "A 30 Minute Project Makeover Using Continuous," Verilab, Inc., 2012.

View Full Article: