testing the refactoring as for formal semantics is dealt with as a test. Refactoring engines like Eclipse, Netbeans and many other contains various kinds of refactoring techniques like move, inline, copy, extract method etc. Usually, developers used to write the test cases to control their refactoring implementations. Few automated testing techniques are used for testing the refactoring implementations of object-oriented systems. In existing, the pre-conditions are recognized and stated that they are extremely stable. In earlier, the testing is done in JRRT (jastAdd refactoring tool) using the process of Alloy Analyzer and the JDolly technique. Using the similar process and techniques, the proposed work makes, testing on the refactoring implementations in the Netbeans Refactoring Engine. Creating the meta-models using the Alloy Analyzer and generating the programs from the model by using the JDolly program generator for applying the testing concept on it. Test Oracles are involved to retain the nature of the programs after implementing the refactoring concept.

Alloy meta-models, Automated testing, Program generation, Refactoring implementations.

[1] M. Schafer and O.de Moor, “Specifying and implementing refactorings,” in proceedings of the 25th ACM International Conference on Object-Oriented Programming, Systems, Languages, and Applications, ser. OOPSLA’ 10. ACM, 2010, pp. 286-3-1.
[2] W.F.O pdyke, "Refactoring Object-Oriented Frameworks,"Ph.D. dissertation, Univ. of Illinois at Urbana-Champaign, 1992.
[3] Melina Mongiovi Member, IEEE, Rohit Gheyi, Gustavo Soares, Márcio Ribeiro, Paulo Borba and Leopoldo Teixeira” Detecting overly strong preconditions in refactoring engines”, IEEE Transactions on Software Engineering DOI 10.1109, 2007.
[4] G. Soares, R. Gheyi, D. Serey, and T. Massoni, “Making program refactoring safer,” IEEE Software, vol. 27, pp. 52–57, 2010.
[5] D. Jackson, I. Schechter, and H. Shlyahter, “Alcoa: the Alloy constraint analyzer,” in Proceedings of the 31st International Conference on Software Engineering, ser. ICSE ’00. IEEE Computer Society, 2000, pp. 730–733.
[6] G. Soares, M. Mongiovi, and R. Gheyi, “Identifying overly strong conditions in refactoring implementations,” in Proceedings of the 27th IEEE International Conference on Software Maintenance, ser. ICSM ’11. IEEE Computer Society, 2011, pp. 173–182.
[7] D. Soares, R. Gheyi, and T. Massoni, “Automated behavioral testing of refactoring engines,” IEEE Transactions on Software Engineering, vol. 39, pp. 147–162, 2013.
[8] Liangliang kong “Essential of unit testing tool for special testing.”IEEE xplore, 2008.
[9] D. S. Rosenblum, “A Practical Approach to Programming with Assertions”, IEEE transactions on software engineering, vol21(1),1995,pp.1
[10] M. Mongiovi, G. Mendes, R. Gheyi, G. Soares, and M. Ribeiro, “Scaling testing of refactoring engines,” in Proceedings of the 30th IEEE International Conference on Software Maintenance and Evolution, ser. ICSME ’14. IEEE Computer Society, 2014, pp. 371–380.
[11] Brett Daniel Danny Dig Kely Garcia Darko Marinov “Automated Testing of Eclipse and NetBeans Refactoring Tools”
[12] Narendar Reddy kancharla, Ananda Rao Akepogu, Gopi chand merugu, Kiran kumar Jogu “ A Quantitative methods to detect design defects after refactoring” in software engineering research and practice 2008.
[13] M. Monogivi, R. Gheyi, G. Soares, L. Teixeira, and P. Borba, “Making refactoring safer through impact analysis”, science of ComputerProgramming, vol. 93, pp. 39-64, 2014.
[14] G. Fraser and A. Arcuri, “EvoSuite: automatic test suite generation for object-oriented software,” in proceedings of the 19th European Conference on Foundations of software Engineering, ser. FSE ’11 ACM, 2011, pp.416-419.