Skip to main content

Automated testing

 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

Popular posts from this blog

Testing Types

         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...

Install Jenkins and configure it to Run Maven with TestNg Selenium

Steps to Install Jenkins and configure it to Run Maven with TestNg Selenium Installation Step 1)  Go to  http://jenkins-ci.org/ and download correct package for your OS. Install Jenkins. Step 2)  Unzip Jenkins to specified folder. Run exe file as shown in following screenshot: Step 3)  In  Jenkins 1.607 Setup  window click on  Next  button. Step 4)  Click on  Install  button in the end. Step 5)  Once installation is done, navigate to the Jenkins Dashboard (http://localhost:8080 by default) in the browser window. Step 6)  Click on the  New Item  link to create a CI job. Step 7)  Select the Maven project radio button as shown in the following screenshot: Using the Build a  Maven Project  option, Jenkins supports building and testing Maven projects. Step 6)  Click on OK button. A new job with name "WebdriverTest" is created in Jenkins Dashboard. Step 7) ...

Clickjacking

Clickjacking Clickjacking  ( User Interface redress attack ,  UI redress attack ,  UI redressing ) is a  malicious technique  of tricking a  Web   user  into clicking on something different from what the user perceives they are clicking on, thus potentially revealing  confidential  information or taking control of their computer while clicking on seemingly innocuous  web pages . It is a  browser security  issue that is a  vulnerability  across a variety of  browsers  and  platforms . A clickjack takes the form of embedded  code  or a script that can execute without the user's knowledge, such as clicking on a  button  that appears to perform another function. [5]  The term "clickjacking" was coined by Jeremiah Grossman and Robert Hansen in 2008. [ citation needed ]  Clickjacking can be understood as an instance of the  confused deputy problem . [6] ...