Beruflich Dokumente
Kultur Dokumente
Volume: 3 Issue: 5
ISSN: 2321-8169
3006 - 3009
_______________________________________________________________________________________________
Rajiv Munjal
Abstract A primary function of assessment would be to find application downfalls to ensure that flaws can be identified and corrected.
Assessment are unable to determine that the merchandise features properly underneath many problems however can certainly only determine
that no operate properly underneath particular problems. This extent regarding application assessment typically involves study of code and also
performance of their code in numerous surroundings and problems and also reviewing the actual areas of code: will it carry out what exactly it
can be supposed to carry out and carry out what exactly it requires to complete.
Keywords-Automation assessment, assessment methods, matlab, mlunit tool
__________________________________________________*****_________________________________________________
I.
INTRODUCTION
Environment Support
Ease of use
Testing associated with Data bank
Object id
Image Assessment
Error Healing Assessment
Object Mapping
Scripting Vocabulary Utilised Support regarding
numerous kinds associated with examination : such as
well-designed, examination administration, cell phone,
and so forth...
Support regarding a number of assessment frameworks
Easy for you to debug the automation computer software
scripts
Ability to realize physical objects in different atmosphere
Extensive examination studies and also benefits
Minimize instruction cost associated with decided on
equipment
1
IJRITCC | May 2015, Available @ http://www.ijritcc.org
_______________________________________________________________________________________
ISSN: 2321-8169
3006 - 3009
_______________________________________________________________________________________________
III.
FRAME WORK
IV.
Framework in Automation
A construction is placed associated with automation tips that
really help with[15]
Maintaining regularity associated with Examining
Improves check structuring
Minimum using code
Less Maintenance associated with code
Improve re-usability
Non Technical testers may be involved with code
Training period of with all the device may be lessened
Reliable in results
Ensure Consistency
Improves accuracy
Increases Efficiency
PROPOSED IMPLEMENTATION
2
IJRITCC | May 2015, Available @ http://www.ijritcc.org
_______________________________________________________________________________________
ISSN: 2321-8169
3006 - 3009
_______________________________________________________________________________________________
Tag Product Tests
Write Tests using shared Fixture
Create Standard Test using Shared Fixture
Create Sophisticated Custom made Fixture
Create Standard Parameterized Test
Create Sophisticated Parameterized Test
Run-Based Unit Tests
Run test packages inside the assessment framework
All testing within a bundle
All testing within a class
All testing within a folder
fib(x)
function y = fib(x)
% Simple queue implementation of Fibonacci function..
if x < 0 || (int64(x) ~= x)
error('invalid input: please input only non-negative
integers.');
end
if x < 2, y = x; return;
end
q = [0 1];
for k = 2:x
q = [q sum(q)];
q(1) = [];
end
y = q(2);
when we call fib function
VI.
Fig. 1
USING MLUNIT
The purpose was to add support for the new "classdef" style
classes in MATLAB 2008a[28]. Creating tests involves
subclassing a class named TestCase, then adding methods
whose names begin with "test". Inside each method you can
rited
validation
methods
(assert,
assertEquals,
assertNotEquals) to check for success or failure. All tests are
run automatically and their results recorded and reported after
the run[30].
Example of Function Based Unit Test:
Testing Fibonacci function
We all know the Fibonacci series
0 1 1 2 3 5 8 13
In which we always consider the sum of last two number at
third location
Loc1
0
Loc2
Loc3
1(Loc1 + Loc2)
Loc4
2(Loc2 + Loc3)
Loc5
3(Loc3 + Loc4)
Loc6
5(Loc4 + Loc5)
Loc7
8(Loc5 + Loc6)
Loc8
13(Loc6 + Loc7)
Fig. 2
Testing fib using mlunit
test_fib.m
function self = test_fib(name)
%test_fib constructor.
%
% Class Info / Example
% ====================
% The class test_fib is the fixture for all tests of the testdriven
% Fibonacci. The constructor shall not be called directly, but
through
% a test runner.
tc = test_case(name);
3
_______________________________________________________________________________________
ISSN: 2321-8169
3006 - 3009
_______________________________________________________________________________________________
self = class(struct([]), 'test_fib', tc);
<properties/>
test_null.m
function self = test_null(self)
%test_null checks, whether the return value of fib(0) is 0.
assert_equals(0, fib(0));
test_value.m
function self = test_value(self)
%test_value tests different values of the fibonacci function (y
= fib(x)).
assert_equals(1, fib(1));
assert_equals(1, fib(2));
assert_equals(2, fib(3));
assert_equals(3, fib(4));
assert_equals(5, fib(5));
assert_equals(8, fib(6));
assert_equals(13, fib(7));
assert_equals(21, fib(8));
assert_equals(34, fib(9));
assert_equals(55, fib(10));
test_value1.m
function self = test_value1(self)
%test_value1 tests different values of the fibonacci function (y
= fib(x)).
assert_equals(0, fib(1));
After Running mlunit test result will be as follow
Automation
setup[16].
increases
rate
involving
examination
VIII. CONCLUSION
_______________________________________________________________________________________
ISSN: 2321-8169
3006 - 3009
_______________________________________________________________________________________________
conditions repeatedly can be taken care of through automation
computer software in automation tests.
REFERENCES
[1] Artem, M., Abrahamsson, P., & Ihme, T. (2009). LongTerm Effects of Test-Driven Development A case study. In:
Agile Processes in Software Engineering and Extreme
Programming,10th International Conference, XP 2009,. 31,
pp. 13-22. Pula, Sardinia, Italy: Springer.
[2] Bach, J. (2000, November). Session based test
management. Software testing and quality engineering
magzine(11/2000),
( http://www.satisfice.com/articles/sbtm.pdf).
[3] Bach, J. (2003). Exploratory Testing Explained, The Test
Practitioner 2002,
(http://www.satisfice.com/articles/et-article.pdf).
[4] Bach, J. (2006). How to manage and measure exploratory
testing. Quardev Inc.,
(http://www.quardev.com/content/whitepapers/how_measur
e_exploratory_testing.pdf).
[5] Basilli, V., & Selby, R. (1987). Comparing the
effectiveness of software testing strategies. IEEE Trans.
Software Eng., 13(12), 1278-1296.
[6] Berg, B. L. (2009). Qualitative Research Methods for the
Social Sciences (7th International Edition) (7th ed.).
Boston: Pearson Education.
[7] 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. 215-242. Recife: Springer.
[8] Bertolino, A. (2007). Software Testing Research:
Achievements Challenges Dreams. In:International
Conference on Software Engineering, ISCE 2007, (pp. 85103). Minneapolis:IEEE.
[9] 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. 393-401). Paris:
IEEE Computer Society.
[10] Chillarege, R. (1999). Software Testing Best Practices.
Tehcnical Report RC2145, IBM.
[11] Frankl, P. G., & Hamlet, R. G. (1998). Evaluating Testing
Methods by Delivered Reliability. IEEE Trans. Software
Eng., 24(8), pp. 586-601.
[12] Galin, D. (2004). Software Quality Assurance: From theory
to implementation. Pearson Education Ltd.
[13] Butts, K., et. al., Automotive Powertrain Control
Development Using CACSD, Perspectives in Control:
New Concepts and Applications, Tariq Samad (ed.), IEEE
Press, 1999.
[14] Butts, K., Toeppe, S., Ranville, S., Specification and
Testing of Automotive Powertrain Control System
Software using CACSD tools, 1998, Proceedings of the
17th AIAA/IEEE/SAE Digital Avionics System
Conference
[15] Toeppe, S., Ranville, S., Model Driven Automatic Unit
Testing Technology: Tool Architecture Introduction and
[16]
[17]
[18]
[19]
[20]
[21]
[22]
[23]
[24]
[25]
[26]
[27]
[28]
[29]
[30]
[31]
Overview,
1999,
Proceedings
of
the
18th
AIAA/IEEE/SAE Digital Avionics System Conference
Toeppe, S., Ranville, S., An Automated Inspection Tool
For a Graphical Specification and Programming
Language, 1999, Quality Week Conference
Toeppe, S., Ranville, S., Bostic, D., Rzeimen, K.,
Automatic Code Generation Requirements For Production
Automotive Powertrain Applications, 1999, IEEE
International Symposium on Computer Aided Control
System Design
Toeppe, S., Ranville, S., Bostic, D., Wang, C., Practical
Validation of Model Based Code Generation for
Automotive Applications, 1999, Proceedings of the 18th
AIAA/IEEE/SAE Digital Avionics System Conf.
Patel, S., Smith, P., Sun, W., Ramanan, R., Donald, H.,
Toeppe, S., Ranville, S., Bostic, D., Butts, K., CACSD in
Production Development: An Engine Control Case Study,
2000, Global Powertrain Conference
Toeppe, S., Ranville, S., Bostic, D., "Automating Software
Specification, Design and Synthesis for Computer Aided
Control System Design Tools", 2000, Proceedings of the
19th AIAA/IEEE/SAE Digital Avionics System Conf.
Chilenski, J. J., Miller, S., Applicability of modified
condition/decision coverage to software testing, 1994,
Software Engineering Journal
Biezer, B., Software Testing Techniques, Second Edition,
International Thomson Computer Press, 1990
The Mathworks, www.mathworks.com
WindRiver, www.windriver.com
ETAS, www.etasinc.com
I-Logix, www.ilogix.com
Rational, www.rational.com
ADI, www.adi.com
T-VEC, www.t-vec.com
http://sourceforge.net/p/mlunit/mlunit/HEAD/tree/trunk/
http://in.mathworks.com/help/matlab/write-unit-tests1.html
5
IJRITCC | May 2015, Available @ http://www.ijritcc.org
_______________________________________________________________________________________