Implementation of Automated Testing in Matlab using MLUnit Tool

Size: px

Start display at page:

Download "Implementation of Automated Testing in Matlab using MLUnit Tool"

Austen Roberts
5 years ago
Views:

1 Implementation of Automated Testing in Matlab using MLUnit Tool Priyanka Narang 1 & Mr. Saurabh Charaya 2 1 M. Tech Scholar, Department Of Computer Engineering 2 H.O.D. (CSE), Department Of Computer Science & Engineering 1,2 Om Institute of Technology & Management, Hisar Abstract: Validation and verification of the code is required because of ever-increasing complexity of embedded software applications, and the emergence of safety critical applications. Several embedded software development groups are using models and doing up front engineering before testing on final product to address this need. Use of old style of testing late in the development cycle resulted in very expensive release cycles. I. Introduction Object-oriented technology has become more and more popular in several various contexts. The Objectoriented paradigm is applied in the areas of programming languages, user interfaces, databases, design and specification methodologies. OOPS based languages are widely applied in industry, and several commercial applications are developed and designed and with object oriented technology. Object-oriented software quality has undergone a rapid change during the last years as a consequence, the attitude towards Several analysis and design methodologies state that a well-designed objectoriented system would only need minimal testing. The object oriented paradigm has been considered powerful enough to assure software quality without any additional effort. It is not enough to guarantee the quality of software products although object-orientation enforces many important programming principles, such as modularity, encapsulation, and information hiding, Object oriented software contains errors just like traditional code it is known to both practitioners and researchers. Due to their peculiarities object oriented systems present new and different problems with respect to traditional programs. II. LITERATURE REVIEW QUANTITATIVE ANALYSIS OF AUTOMATION AND MANUAL TESTING In this research he started that Testing is a major activity in software development process to find defect in software. Testing can be conducted manually as well as automated. Various types of metrics are collected during software development process & software testing process. These metrics provide quantitative approach to analyze any process of software engineering. This paper presents concept of automation & manual testing & problem within manual testing & profit of automatic testing. This paper also represents analysis of automation & manual testing based on some testing metrics. The main objective in research paper is to focus on, effectiveness & importance of automation testing. Ali Javed 1, Muazzam Maqsood, March 2012 How To Improve Software Quality Assurance In Developing Countries Quality is an important factor in software industry. Software quality depends upon the customer satisfaction which can be achieved through applying standards. In this era achieving quality software is very important because of the high customer demands. Developed countries are excelling in software industry and improving day by day. Meanwhile developing countries like Pakistan are struggling with software quality and cannot maintain reputation in International Market. Software Quality lacks due to many reasons. This paper will address the problems for lacking interest in improving the ISSN Page 209

2 software quality by higher authorities and software assurance team. We have provided solution to the addressed problems also. Ashwin B. Tomar1 and Dr.Vilas. M. Thakare 4, October 2011 A SYSTEMATIC STUDY OF SOFTWARE QUALITY MODELS This paper aims to provide a basis for software quality model research, through a systematic study of papers. It identifies nearly seventy software quality research papers from journals and classifies paper as per research topic, estimation approach, study context and data set. The paper results combined with other knowledge provides support for recommendations in future software quality model research, to increase the area of search for relevant studies, carefully select the papers within a set of journals, and conduct more studies on methods used by software industry and researchers. Researcher has predicted quality by proposing models using different approach, methodology, algorithm, techniques. They have evaluated model through case study, experiment, experts, opinions and survey. Chayanika Sharma1, Sangeeta Sabharwal2, Ritu Sibal3 1, January 2013 A Survey on Software Testing Techniques using Genetic Algorith The overall aim of the software industry is to ensure delivery of high quality software to the end user. To ensure high quality software, it is required to test software. Testing ensures that software meets user specifications and requirements. However, the field of software testing has a number of underlying issues like effective generation of test cases, prioritisation of test cases etc which need to be tackled. These issues demand on effort, time and cost of the testing. Different techniques and methodologies have been proposed for taking care of these issues. Use of evolutionary algorithms for automatic test generation has been an area of interest for many researchers. Genetic Algorithm (GA) is one such form of evolutionary algorithms. In this research paper, we present a survey of GA approach for addressing the various issues encountered during software testing. In this paper, applications of GA in different types of software testing are discussed. Maneela Tuteja, Gaurav Dubey 3, July 2012 A Research Study on importance of Testing and Quality Assurance in Software Development Life Cycle (SDLC) Models In recent years, software testing is becoming more popular and important in the software development industry. Indeed, software testing is a broad term encircling a variety of activities along the development cycle and beyond, aimed at different goals. Hence, software testing research faces a collection of challenges. A consistent roadmap of most relevant challenges is proposed here. In it, the starting point is constituted by some important past achievements, while the destination consists of two major identified goals to which research ultimately leads, but which remains as reachable as goals. The routes from the achievements to the goals are paved by outstanding research challenges, which are discussed in the paper along with the ongoing work. Software testing is as old as the hills in the history of digital computers. III. Automated Testing: Process, Planning, Selection of tools Manual testing is performed by a human in front of a computer carefully executing the test steps. Using an automation tool to execute your test case suite is Automation Testing. The automation software can also enter test data into the System under Test, compare expected and actual results and generate test reports. Test Automation demands considerable investments of money and resources. Successive development cycles will require execution of same test suite again and again. Using a test automation tool it's possible to record this test suite and re-play it as required. No human intervention is required once the test suite is automated. This improved ROI of Test Automation. ISSN Page 210

3 Purpose of Automation is to reduce number of test cases to be run manually and not remove manual testing all together. Benefits of Automated Testing Automated testing is essential due to following reasons: Manual Testing is time and cost consuming It s difficult to test for multi lingual sites manually Automation does not need Human intervention. You can run automated test unattended (overnight) Automation boosts speed of test execution Automation helps boosting Test Coverage Manual Testing can become boring and error prone. IV. PROPOSED QUALITY MODEL Issues with xunit Tool As of R2013a (March 2013), MATLAB includes a unit test framework. There are no plans to continue further development of MATLAB xunit.. MATLAB xunit is designed to be easy to use for MATLAB users with a wide range of experience. Users can write tests using ordinary M-files that are very simple in structure.[28] MATLAB xunit comes with extensive documentation that ranges in scope from a "Getting Started" section to advanced techniques and architectural notes. You can view this documentation online without downloading the package. For example, scroll down to the "Published M Files" section on this page and click on "MATLAB xunit Quick Start - How to write and run tests." To see all the MATLAB xunit documentation online, scroll down to the "HTML Files" section on this page and click on "Readme.html." Only the "xunit" directory is needed to use the framework. The "tests" directory contains the framework's own test suite. The "architecture" directory contains architectural notes on the framework's design and how it might be extended. MATLAB xunit can be used with MATLAB releases R2008a and later. MATLAB xunit relies heavily on object-oriented language features introduced in R2008a and will not work with earlier releases. User-Defined Functions A user-defined function is a Matlab program that is created by the user, saved as a function file, and then can be used like a built-in function. A function in general has input arguments (or parameters) and output variables (or parameters) that can be scalars, vectors, or matrices of any size. There can be any number of input and output parameters, including zero. Calculations performed inside a function typically make use of the input parameters, and the results of the calculations are transferred out of the function by the output parameters.[28] Classification systems and design patterns enable engineers and scientists to make sense of complex systems and to reuse efforts by others. Object-oriented programming (OO) applies to software development the standard science and engineering practice of identifying patterns and defining a classification system describing those patterns. The OO approach improves your ability to manage software complexity particularly important when developing and maintaining large applications and data structures by applying classification systems and design patterns to programming, Class[3] classdef Syntax Class definitions are blocks of code that are denoted by the classdef keyword at the beginning and the end keyword at the end. Files can contain only one class definition. The following diagram shows the syntax of a classdef block. Only comments and blank lines can precede the classdef key word. V. IMPLEMENTATION Function based testing Code of Prime.m function primalitytest = prime(n) m = 2; % initialise factor to test flag=0; ISSN Page 211

for m = 2:floor(sqrt(n)) if mod(n,m) == 0 %m is a factor of n flag=1; end end; if(flag==1) primalitytest='no'; else primalitytest='yes'; end 5.

3 Creating Test Case for MLUnit [4] test_cl1.m function self = test_cl1(name) %test_cl1 constructor.

The constructor shall not be called directly, but through % a test runner. tc = test_case(name); self = class(struct([]), 'test_cl1', tc); Fig 1 Output of fib.

4 for m = 2:floor(sqrt(n)) if mod(n,m) == 0 %m is a factor of n flag=1; end end; if(flag==1) primalitytest='no'; else primalitytest='yes'; end 5.2 Class based Testing Testing using assert keyword assert_equals(81,sq(y)) p = 81 Testing by passing wrong value assert_equals(82,sq(y)) p = Creating Test Case for MLUnit [4] test_cl1.m function self = test_cl1(name) %test_cl1 constructor. % % Class Info / Example % ==================== % The class test_cl1 is the fixture for all tests of the test-driven % cl1. The constructor shall not be called directly, but through % a test runner. tc = test_case(name); self = class(struct([]), 'test_cl1', tc); Fig 1 Output of fib.m file Step 2: Now create another file test value.m Fig 2 Output of test value.m Step 3: Create test_null.m Output for Simple Test Case Using Functions Step 1: Create test_fib.m file in this folder Fig.3 Output of test null.m Step 4: create test_value1.m ISSN Page 212

5 [5] Bach, J. (2000, November). Session based test management. Software testing and quality engineering magzine(11/2000) [6] Bach, J. (2003). Exploratory Testing Explained, The Test Practitioner 2002, Fig 4 Output of testing test_value1.m VI. Conclusions There is a major need for more upfront engineering in today s embedded software design process. Very little upfront testing has been done within the automotive area. With the introduction of executable modeling tools such as MLUnit this upfront testing is more feasible. It is the work of the tool vendors to make this testing technology available and practical to the user. References [1] Object Oriented software testing by Devid C. Kung /COMP595VAV/OOSWTesting.pdf [2] Automated Testing tools International Conference, XP 2009,. 31, pp Pula, Sardinia, Italy: Springer. [3] Matlab Documentation. Software testing and quality engineering magzine(11/2000) [4] Artem, M., Abrahamsson, P., & Ihme, T. (2009). Long-Term Effects of Test-Driven Development A case study. In: Agile Processes in Software Engineering and Extreme Programming,10th International Conference, XP 2009,. 31, pp Pula, Sardinia, Italy: Springer. [7] Bach, J. (2006). How to manage and measure exploratory testing. Quardev Inc., [8] Basilli, V., & Selby, R. (1987). Comparing the effectiveness of software testing strategies. IEEE Trans. Software Eng., 13(12), [9] Berg, B. L. (2009). Qualitative Research Methods for the Social Sciences (7th International Edition) (7th ed.). Boston: Pearson Education. [10] Bernat, G., Gaundel, M. C., & Merre, B. (2007). Software testing based on formal specifications: a theory and tool. In:Testing Techniques in Software Engineering, Second Pernambuco Summer School on Software Engineering. 6153, pp Recife: Springer. [11] Bertolino, A. (2007). Software Testing Research: Achievements Challenges Dreams. In: International Conference on Software Engineering, ISCE 2007, (pp ). Minneapolis: IEEE. [12] Causevic, A., Sundmark, D., & Punnekkat, S. (2010). An Industrial Survey on Contemporary Aspects of Software Testing. In: Third International Conference on Software Testing, Verification and Validation (pp ). Paris: IEEE Computer Society. ISSN Page 213

6 [13] Chillarege, R. (1999). Software Testing Best Practices. Tehcnical Report RC2145, IBM. [14] Frankl, P. G., & Hamlet, R. G. (1998). Evaluating Testing Methods by Delivered Reliability. IEEE Trans. Software Eng., 24(8), pp [15] Galin, D. (2004). Software Quality Assurance: From theory to implementation. Pearson Education Ltd. [16] Butts, K., et. al., Automotive Powertrain Control Development Using CACSD, Perspectives in Control: New Concepts and Applications, Tariq Samad (ed.), IEEE Press, [17] Butts, K., Toeppe, S., Ranville, S., Specification and Testing of Automotive Powertrain Control System Software using CACSD tools, 1998, Proceedings of the 17 th AIAA/IEEE/SAE Digital Avionics System Conference [19] Toeppe, S., Ranville, S., Model Driven Automatic Unit Testing Technology: Tool Architecture Introduction and Overview, 1999, Proceedings of the 18 th AIAA/IEEE/SAE Digital Avionics System Conference ISSN Page 214

Code Complete 2: A Decade of Advances in Software Construction Construx Software Builders, Inc. All Rights Reserved.

Code Complete 2: A Decade of Advances in Software Construction www.construx.com 2004 Construx Software Builders, Inc. All Rights Reserved. Construx Delivering Software Project Success Introduction History