Skip to main content

Automated testing

By

 Automated testing

Main article: Test automation
Many programming groups are relying more and more on automated testing, especially groups that use test-driven development. There are many frameworks to write tests in, and continuous integration software will run tests automatically every time code is checked into a version control system.
While automation cannot reproduce everything that a human can do (and all the ways they think of doing it), it can be very useful for regression testing. However, it does require a well-developed test suite of testing scripts in order to be truly useful.
Testing tools
Program testing and fault detection can be aided significantly by testing tools and debuggers. Testing/debug tools include features such as:
·        Program monitors, permitting full or partial monitoring of program code including:
·         Instruction set simulator, permitting complete instruction-level monitoring and trace facilities
·         Program animation, permitting step-by-step execution and conditional breakpoint at source level or in machine code
·         Code coverage reports
·        Formatted dump or symbolic debugging, tools allowing inspection of program variables on error or at chosen points
·        Automated functional GUI testing tools are used to repeat system-level tests through the GUI
·        Benchmarks, allowing run-time performance comparisons to be made
·        Performance analysis (or profiling tools) that can help to highlight hot spots and resource usage
Some of these features may be incorporated into an Integrated Development Environment (IDE).
·        A regression testing technique is to have a standard set of tests, which cover existing functionality that results in persistent tabular data, and to compare pre-change data to post-change data, where there should not be differences, using a tool like diffkit. Differences detected indicate unexpected functionality changes or "regression".

Comments

Post a Comment

Popular posts from this blog

Testing Types

By
         Installation testing Main article: Installation testing An installation test assures that the system is installed correctly and working at actual customer's hardware. Compatibility testing Main article: Compatibility testing A common cause of software failure (real or perceived) is a lack of its compatibility with other application software, operating systems (or operating system versions, old or new), or target environments that differ greatly from the original (such as a terminal or GUI application intended to be run on the desktop now being required to become a web application, which must render in a web browser). For example, in the case of a lack of backward compatibility, this can occur because the programmers develop and test software only on the latest version of the target environment, which not all users may be running. This results in the unintended cons...
Post a Comment
Read more

What really happens when you navigate to a URL

By
As a software developer, you certainly have a high-level picture of how web apps work and what kinds of technologies are involved: the browser, HTTP, HTML, web server, request handlers, and so on. In this article, we will take a deeper look at the sequence of events that take place when you visit a URL. 1. You enter a URL into the browser It all starts here: 2. The browser looks up the IP address for the domain name   The first step in the navigation is to figure out the IP address for the visited domain. The DNS lookup proceeds as follows: Browser cache –  The browser caches DNS records for some time. Interestingly, the OS does not tell the browser the time-to-live for each DNS record, and so the browser caches them for a fixed duration (varies between browsers, 2 – 30 minutes). OS cache  – If the browser cache does not contain the desired record, the browser makes a system call (gethostbyname in Windows). The OS has its own cache....
Post a Comment
Read more

Software Testing Basics - Software Testing Interview Questions and Answers

By
1. Can you explain the PDCA cycle and where testing fits in? Software testing is an important part of the software development process. In normal software development there are four important steps, also referred to, in short, as the PDCA (Plan, Do, Check, Act) cycle. Let's review the four steps in detail. Plan:  Define the goal and the plan for achieving that goal. Do/Execute:  Depending on the plan strategy decided during the plan stage we do execution accordingly in this phase. Check:  Check/Test to ensure that we are moving according to plan and are getting the desired results. Act:  During the check cycle, if any issues are there, then we take appropriate action accordingly and revise our plan again. So developers and other stakeholders of the project do the "planning and building," while testers do the check part of the cycle. Therefore, software testing is done in check part of the PDCA cyle. 2. What is the difference between white box,...
Post a Comment
Read more