Вы находитесь на странице: 1из 5

What is functional testing?

It's a type of GUI testing where functionality of an application is tested. To be specific: Testing of all features and functions of a system [software, hardware, etc.] to ensure requirements and specifications are met. Functionality testing of software is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. Functionality testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic

or
Functional testing is a process of testing all the functionality of an application.When we create a software, we create it keeping the users of that software in mind. Functional testing test whether the application fulfills the requirement of the user. It means to check whether the functionality of an application are working as expected or not. For example, Login functionality, Compose mail functionality, Delete mail functionality,etc.

what is Gui testing? Gui means Graphical User Interface we will conduct this Test manually. During this test we will validates the Screens i.e controls alignment, appearence etc. Basically we will check the user friendlyness of the screens. Or In software engineering, graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its written specifications.GUI testing involves carrying set of tasks and comparing the result of same with the expected output and ability to repeat same set of tasks multiple times with different data input and same level of accuracy. GUI Testing includes how the application handles keyboard and mouse events, how different GUI components like menubars, toolbars, dialogs, buttons, edit fields, list controls, images etc. reacts to user input and whether or not it performs in the desired manner.

Compatibility testing
Compatibility testing, part of software non-functional tests, is testing conducted on the application to evaluate the application's compatibility with the computing environment. Computing environment may contain some or all of the below mentioned elements: Or

Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware Test Procedure: Detailed instructions document for the set-up, execution, and evaluation of results for a given test case. This document contains a set of associated instructions. This documentation may have steps specifying a sequence of actions for the execution of a test
Or A test procedure is a formal specification of test cases to be applied to one or more target

program modules. Test procedures are executable. A process called the VERIFIER applies a test procedure to its target modules and produces an exception report indicating which test cases, if any, failed. Test procedures facilitate thorough software testing by allowing individual modules or arbitrary groups of modules to be thoroughly tested outside the environment in which they will eventually reside. Test procedures are complete, self-contained, self-validating and execute automatically. Test procedures are a deliverable product of the software development process and are used for both initial checkout and subsequent regression testing of target program modifications. Test procedures are coded in a new language called TPL (Test Procedure Language). The paper analyzes current testing practices, describes the structure and design of test procedures and introduces the Fortran Test Procedure Language.

Test Scenarios
Scenario testing is a software testing activity that uses scenarios: hypothetical stories to help the tester work through a complex problem or test system. The ideal scenario test is a credible, complex, [1] compelling or motivating story the outcome of which is easy to evaluate. These tests are usually different from test cases in that test cases are single steps whereas scenarios cover a number of step

A test case in software engineering is a set of conditions or variables under which a tester will
determine whether an application or software system is working correctly or not. The mechanism for determining whether a software program or system has passed or failed such a test is known as a test oracle. In some settings, an oracle could be a requirement or use case, while in others it could be a heuristic. It may take many test cases to determine that a software program or system is considered sufficiently scrutinized to be released. Test cases are often referred to as test scripts, particularly when written. Written test cases are usually collected into test suites

Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test

reporting functions. Commonly, test automation involves automating a manual process already in place that uses a formalized testing process.

[1]

Test execution
A test execution engine is a type of software used to test software, hardware or complete systems.
Result analzing:The Test Results Viewer helps you manage, visualize, inspect, and analyze the data in your test results using multiple plot types, including line, surface, scatter, time series, waterfall and image. Or Analysis is the process of breaking a complex topic or substance into smaller parts to gain a better

understanding of it. The technique has been applied in the study of mathematics and logic since before Aristotle (384322 B.C.), though analysis as a formal concept is a relatively recent development

Defect reporting and tracking


A Defect is a non-conformance of Deliverables to Specification. Defects can be found by testers, project team members or you. No matter who identifies a Defect, it has to be removed. Defects are stored in Defect Tracking System. Every customer will have access to this online system.

Test Data

The data to be used for this module testing would be any music files in MP3 format.

Test Procedures

Testing PGP includes two main stages, first stage tests the encryption process and seconds stage involves testing the decryption process. In these stages, the data (MP3 file) will be encrypted or decrypted using three different key strengths; 1. 512 bits: Low commercial grade, fast but less secure. 2. 768 bits: High commercial grade, medium speed and good security. 3. 1024 bits: Military grade, slow but offers highest security.

After having encrypted or decrypted the data, a utility in CYGWIN (or some files comparison utility in DOS) is used to detect any difference between the data encrypted/ decrypted by the original PGP and the modified PGP (one with I/O system calls removed).

Test Results

After having carried the procedures as mentioned above, we have found that the encrypted/ decrypted data produced by both versions are identical, the test has proven that the original PGP and the modified PGP versions are robust and producing the same results. This concludes that the version, which will be used in the DEEP-3 system is functioned correctly.

Test closure activities : During test closure activities, we collect data from completed test activities to consolidate experience, including checking and filing testware, and analyzing facts and numbers. We may need to do this when software is delivered. We also might close testing for other reasons, such as when we have gathered the infor-mation needed from testing, when the project is cancelled, when a particular milestone is achieved, or when a maintenance release or update is done. Test closure activities include the following major tasks: 1.) Check which planned deliverables we actually delivered and ensure all incident reports have been resolved through defect repair or deferral. 2.) Finalize and archive testware, such as scripts, the test environment, and any other test infrastructure, for later reuse. 3.) Hand over testware to the maintenance organization who will support the software and make any bug fixes or maintenance changes, for use in con firmation testing and regression testing. 4.) Evaluate how the testing went and analyze lessons learned for future releases and projects.
Test design:I believe this is two questions and not one. Design is creating a plan for how to
implement an idea. Technique is a method or way for performing a task. So...

Test Design is creating a set of inputs for a given software that will provide a set of expected outputs. The idea is to ensure enough of the code is working in order to release it with as few problems as possible for the average user. Test Design Technique is how you would implement that. There are various tools available to automate the testing of software, implementing different techniques to ensure test coverage comes close to a 100%.

test plan: A test plan documents the strategy that will be used to verify and ensure that a product

or system meets its design specifications and other requirements. A test plan is usually prepared by or with significant input from Test Engineers. Risk management is the identification, assessment, and prioritization of risks (defined in ISO 31000 as the effect of uncertainty on objectives, whether positive or negative) followed by coordinated and economical application of resources to minimize, monitor, and control the probability and/or [1] impact of unfortunate events or to maximize the realization of opportunities. Risks can come from uncertainty in financial markets, project failures (at any phase in design, development, production, or sustainment life-cycles), legal liabilities, credit risk, accidents, natural causes and disasters as well as deliberate attack from an adversary, or events of uncertain or unpredictable root-cause. Several risk management standards have been developed including the Project Management Institute, [2][3] the National Institute of Science and Technology, actuarial societies, and ISO standards. Methods, definitions and goals vary widely according to whether the risk management method is in the context of project management, security, engineering, industrial processes, financial portfolios, actuarial assessments, or public health and safety. Software testing life cycle (STLC) identifies what test activities to carry out and when (what is the best time) to accomplish those test activities. Even though testing differs between organizations, there is a testing life cycle.

Вам также может понравиться