Functional Testing

Functional testing verifies that the end user gets what he wants from the application. It involves testing to ensure that the tasks or the steps required completing functionality works well. Functional testing involves testing of functional requirements as per the specification.

System testing has classifications like functional and non functional testing. Hence the functional testing is a part of system testing.

System testing allows the testers to test the typical end product. Every single module, interface and every minute detail are needed to be tested in system testing.

Functional testing is aimed at testing the functionalities of the product being tested. These functionalities include volume, stress, load, security, scalability, performance etc. Hardware and software is not concerned with functional testing.

We will send "End to Testing Checklist" and "Test Summary Report". These reports includes what features we cover into the application and defects and other details.

Smoke testing-it is a bulid verification test.

only the essential functionalities will be checked.

Sanity testing-only sanity of code will be checked.

Particular code will be checked before it actually combined to existing system.

To know about the status of the project use RTM

Schedule Variance = Actual Scheduled - Planned Schedule

FRD stands for functional Requirement Document. The first type of testing you would do when the FRD is ready and approved is STATIC TESTING. This involves studying the work documents like the Requirement document itself to see if there are any errors in it before you start your requirement extraction into an Excel Spreadsheet.

At this early stage OD the testing cycle where your Requirement Documents is just being approved, the application under test is most likely not ready, so you can not carry out Smoke Testing or Sanity Testing.

If you donot have much time to test the whole application, then the best approach is by giving priorities to the functions or the modules.

For example, login window of an application has a very high priority, caz it authenticates the user and allows the users to access the application.

Another example, if its a database apllication, you need to check the users rights in the login screen, data storing by checking data addition, deleting and edyting etc.

Functional testing is a type of black box testing that bases its test cases on the specifications of the software component under test. Functions are tested by feeding them input and examining the output, and internal program structure is rarely considered (Not like in white-box testing)

Test Item tree is a data analytical method which allows constructing a hierarchical structure on the items of a questionnaire or test from observed response patterns.

Assume that we have a questionnaire with m items(see below q1,q2,q3, etc..) and that subjects can answer positive (1) or negative (0) to each of these items, i.e. the items are dichotomous. If n subjects answer the items this results in a binary data matrix D with m columns and n rows. Typical examples of this data format are test items which can be solved n(1 )or failed n(2) by subjects. Other typical examples are questionnaires where the items are statements to which subjects can agree (1) or disagree (0).

Black box testing which is otherwise termed as Specification based technique.Hence the major job of this technique is abiding the specification made for the project.This technique is handicapped when the specification is already missing.

Here it is not possible to incident regarding the coding quality and standard.

Black box testing is unaware of the " Coverage " technique .So the percentage of the item exercised by the test case can not be determined.

Functionality testing is testing for requirements. So now tell us wouldn't you like to check if the application adheres to the requirements that client desires as they are paying for the entire project?

Agile method:1)It's highest priority is to satisfy customer through early and continuous delivery of valuable software.

2)changing requirements,sometimes late in development.

3)Delivery of working software frequently,shorter time duration.

4)Business people and developers work throughout the project.

5)Build projects considering few trusted people,by giving support and help in any manner needed for the software to become available.

Module1

Module2

module3

There are 3 modules if you logged in first module then it will move to next next module this is the working function

While we are working if we entered in module 1 then to module 2 then to module 3 then in the last page if we work it should directly break the link and move to first module first page

Back end testing means testing database. testing the inputs properly saved at back end or not.make sure whatever we input data at front end it properly saved at backend. Where as regression testing means repeatedly testing the application to make sure application should reach as per the requirement specification.

There are 3 modules in Retail banks 1. Admin, 2.Banker 3.Customer. I wanted to know, commonly what are the change requirement occurs in these modules(in a already working bank)? Also, provide few test scenarios the respective change requirement?

1.verify that the first field is accepting string.

2.verify that the first field is not accepting any thing other than a text(numbers(purely numbers with out any string data type) null characters, special characters)

3.verify that the second field is accepting float values.

4. verify that the second field is not acepting any thig other than float.

5.verify the output when the above conditions are met, o not.

Functional test cases can be mapped with functional requirement document with the help of Requirement traceability matrix (RTM).

RTM is a document which shouws the mapping of test cases against requirements. So if we want on to trace a test case to a requirement, we can see the mapping in RTM document.