Analysis of Automated Testing tools and their implementation
Keywords:
Automation testing, testing tools, mlunitAbstract
A primary purpose of testing is to detect software failures so that defects may be discovered and corrected. Testing cannot establish that a product functions properly under all conditions but can only establish that it does not function properly under specific conditions. The scope of software testing often includes examination of code as well as execution of that code in various environments and conditions as well as examining the aspects of code: does it do what it is supposed to do and do what it needs to do.
References
Basilli, V., & Selby, R. (1987). Comparing the effectiveness of software testing strategies. IEEE Trans. Software Eng., 13(12), 1278-1296.
Berg, B. L. (2009). Qualitative Research Methods for the Social Sciences (7th International Edition) (7th ed.). Boston: Pearson Education.
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.
Bertolino, A. (2007). Software Testing Research: Achievements Challenges Dreams. In:International Conference on Software Engineering, ISCE 2007, (pp. 85-103). Minneapolis:IEEE.
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.
Chillarege, R. (1999). Software Testing Best Practices. Tehcnical Report RC2145, IBM.
