Few more scenarios for only Login functionality

Here is the list of test cases/Scenarios for Login Page:

Test Scenarios - Login Page
1 . Does User name (6-12 chars) and Password (6-12 chars) field length validation set?
2 . Does the max length set to all the text boxes?
3 . Whether the Password field is masked with asterisks? (*****)
4 . Whether left and right trimming are done for Password field?
5 . Login credentials in UPPER case are not treated as invalid?
6 . Forgot Password link is Present on the form?
7 . When clicked to Reset button, data is cleared from all the text boxes in the form?
8 . Does application shows validation message when special characters are given in the username field?
9 . Does application shows validation message when Invalid username given?
10 . Does application shows validation message when Invalid password given?
11 . Whether application redirects to the Login page when Login URL is bypassed? i.e. by giving the direct next form URL in the browser
12 . When clicked Log out link application goes to Home page?
13 . Does Application shows Validation Message for Blank Username/Password given?
14 . Whether Application redirect to appropriate page for Remember Me?
15 . Whether Application redirect to appropriate page for Forgot password?
16 . Whether Application redirect to appropriate page for Sign Up?

Quality matters than Quantity in Testing

Why Quality is Important in terms of Software Testing.

Hey there are around 100 bugs in your project what would you do?

Will you test all these again and again in a short span of time.

Its about Quality and Time that matters here. Well Identifying most critical Bugs and getting to know what might most effect other Bugs is about Testing good Quality software.

The other Bugs which are not so effected can be Tested in next given cycle at appropriate time.

But the Most Important Bugs has to be tested initially as there will be an release of software approaching soon.

So its the matter of Just getting Good Quality software with an appropriate time which is important than Testing all Bugs which are not appropriate time and schedule.  

Risk Based Testing

Risk Based Testing in Software testing.....

A Risk in general terms is normally meant for Problems or some situation which may occur in future for any task assigned. So In Software Testing also there is category called Risk factor in Software for any given application and for even the company also.

Risk based testing in Software Testing is where we categorize while performing or test a given application where its Cost factor, Team size, Priority of Task assigned, ability of person to handle application for different scenarios or any urgent tasks assigned.

Like for example in real time scenario will be like in a given project if a team develops application having Developers and Testers. A tester writes Test Cases in his own manner but what if he leaves organization, this is called Risk Factor. Because the new Joinee will have to clearly understand from basic in how the previous tester has written the test cases and he has to continue his left over task.

Another example is the cost factor which is major issue where in case if Business Analyst doesnot analyze how much time or how much team is needed for application to develop, in future the same time and cost might be a factor for creating Quality application. This is Risk factor for whole company.

Another example is if the project is assigned for a team and what if the person doesnot have that depth knowledge on the particular technology, this is risk factor where again time and cost will be factor.  

Test Harness

What is Test Harness?

Anybody have come across Test Harness. Well It is kind of code written in the form of WhiteBox Testing. In SDLC Model i.e V Model there is one Level for Testing called as Integration Testing where each modules are been broken into sub modules for testing and integrating components.
One Level in Integration Testing is System Integration Testing. Further in it there are different Strategies in it i.e Top Down approach and Bottom Up analysis.
Here in Top Down approach, Stubs are used and in Bottom Up analysis Drivers are used.
Stubs and Drivers are nothing but set of codes written unless the entire Code is not yet developed.
So if Developer has not yet completed his part of work these Stubs and Drivers are written in functions and procedures.
Hence this set of codes are called as Test Harness.

Tracebility Matrix in Software Testing

What exactly is Traceability Matrix?

First of all by name itself Trace gives the meaning that something has to be traced. Similarly for Software Testing everything has to be traced. In large projects each and every data has to be maintained for future reference. So there is a concept called Traceability Matrix.

So while preparing Traceability Matrix it can be done using Excel sheet or any other Test Management Tool  like Quality Center also. While preparing  Traceability Matrix in Excel these are the main things which need to be concentrated i.e,
Sample Template
Requirements ID  Req ID1.1  Req ID1.2  Req ID1.3  Req ID1.4  Req ID1.5 

Test Cases id
TC1.1
TC1.2
TC1.3
TC1.4
TC1.5

If a Tester leaves the organization and if he doesnot fill the report of   Traceability Matrix, how will the New Tester come to know what and all Test Cases have been written to which Requirement IDs.

So  Traceability Matrix  gives the entire coverage of How many Test Cases have been written, how many Test Cases executed, which defect has been raised on which Test Cases etc.

In Quality Center Test Coverage analysis prepares automatically all the reports and generates it after linkage is done by Testers of Test Cases to Requirements.   

Test Management Tool Quality Center

Quality Center is basically Test Management tool where you can manage your entire Test Data, Test Requirements, Test Cases in short all known as Test Deliverables.

Quality Center contains basically 4 Important Modules in it.

1. Requirements: Here all the Parent and Child requirements are written in Sequential order where every Parent and Child will be having their Unique Id no, which easily in future can be recognized if any changes of requirements will be done.

2. Test Plan: Here is the Module where entire Test Cases are managed in this Module along with Test Data also, apart from this these Test Cases are written in standard Template form. And entire Test Set are managed in this Module where even Export and Import of Excel or other files can be done in this Module. The Test Cases are linked to the Requirements module with their respective Ids.
The Template is i.e
Sl.No  Description   Expected Result  Actual Result  Status

3. Test Lab: Here is the Module where entire Test cases are executed after writing Test Cases it has to be executed so in this module we execute along with Test Data given in excel form. And further for executing the Test Cases it has to be linked to the Test Plan Module with their respective Ids.
Test suite is nothing but collection of Test Cases which can be executed.

4. Defects: Here is the module where entire Defects/Bugs are raised where each and every Bugs has Unique Id assigned to it. Defects can also be raised from test Lab if any execution fails at that time. 

Difference between Smoke Testing, Sanity Testing, Monkey Testing, Ad Hoc Testing

Few Difference between Smoke Testing, Sanity Testing, Monkey Testing, Ad Hoc Testing Concepts

Smoke Testing: This type of Testing is mainly done as the Checking of Basic Functionality when a Build is released and tried to test if Bugs are found in this test immediately Testing is stopped and does not go further for any different types of Testing. Mainly Positive Scenarios are tested

Sanity Testing: This type of Testing is also similar to Smoke Testing But here its type of Width wise Testing and for Checking of Basic Functionality when a Build is released and tried to test with Both Positive and Negative Scenarios if Bugs are found in this test immediately Testing is stopped and does not go further for any different types of Testing.   

Ad Hoc Testing: This type of Testing is done with No proper documentation or writing any Test Cases , here its just testing the application with no standard format.

Monkey Testing:  This type of Testing is done like for example if a Monkey uses some product or application how will he use it, similarly entering some Junk or Random Data in the fields and trying to test it.