No effect man...u can shift to a new company!! But, think
twicw before shifting. Competetion is very high in the
market.  If u think u have enough skills that u can survive
in any company, then u can surely shift to a new
company.Good Luck!!

Hi
Once the tester finds   the issues the tester give the 
status of the issues is NEW
Then the tester assigned to developers then status of 
issues is Assigned 
Then the developers open issues then the status of issues 
is OPEN
After the issues is fixed and gives the modify build 
Then tester testing the issues is fixed are not? If fixed 
the status of issues is FIXED
If you not fixed the status of issues is REOPEN
Some times based on priority and severity the developers 
give and (tester ) status will be changes like deferred

Identifying and Reporting the bug--assign the bug--evolution
of the bug--Fixing the bug0--Verifying the bug----Closing
the bug

this is the bug life cycle.

open 

PM analyses

assigned or defer

developer fixes

fixed

tester checks

checked - if not satisfied, the tester reopens.

tester closes

closed

Hi all,

Bug Life cycle contains many phases

New-When a test engineer raises an issue.

Assigned-Issue will be assigned to the developer.

Fixed-The bug is fixed by the developer.

The bug is retested.If it works fine then Closed will the 
bug life cycle phase.

EXPLAIN BUGLIFECYCLE:



 BUG LIFE CYCLE is the movement of the bug in different stages.
 after understanding the functional requirement specifications 
the developer will develope the module after that it will go
to the testing team.
as a result of testing if any defects are found. then it
will be OPEN/NEW bug. 
if there are no any defects testing will be stopped. again
these open/new bugs
 will be send to the developement team for fixation.then the
developer will see whether 
it is really a defect. if it is really a defect then it will
be rectified.if it is not 
a defect then again there will be 3 stages like HOLD, AS PER
DESIGN, TESTERS ERROR.
 the rectified defect will be again sent to the testing
team. then due to the result 
of the regression testing if the defects are rectified then
it will be CLOSED.
if the defects are not rectified then again it will be
RE-OPEN. this is BUG LIFE CYCLE.

*************

Defect life cycle:first step is to see whether defect is
opened or new.if it is so then first is to see which all
defect is to be rejected ,fixed in new release,not
reproduced etc.and there may be some defects which are small
at the core of application that defects cant be fixed..some
are not reproducible for example were environment is
mismatch or build is mismatch in such case it is not
reproducible.
so 1)OPEN/NEW
   2)ASSIGNED 
   3) FIXED
   4) RETESTED
   5)OPEN /CLOSE..
thank u...............

NEW--> when the tester find the error or mistakes in the 
application
ASSIGNED-->It will be assigned to the developer who 
developed the application
FIXED--> The status of the bug will as fixed after it fixed 
by the developer
VERIFY--> It should be verified by the tester once it fixed 
and it will be REOPENED only if the bug remains the same or 
else
CLOSED--> It will be closed

BLC
New this is new status of new applications. Done by a TE.
Open if any defect found this status set to open condition,
send to developer done by a TL
Fix after rectify the defect if status change to fix, send
to tester. Done by a Developer.
Reopen if any defect found again this status change to
reopen condition done by a TE/TL.
Close all defects rectify this status change to close stage.
Done by a TE/ TL.

In web testing two main aspects are link coverage and
content coverage which are not applicable for client/server
application.

In link coverage test engineers are validating links are in
correct place are not and those links providing next pages
correct are not.

In content coverage test engineers are validating the
content of web page with respect to client provided text.

In my Opinion we do URL Testing for Web-Based Applications 
which we don't do in Client-Server Application.

There is not much difference between client server and web 
based applications testing. The main difference is URL 
testing and browser compatiblity testing is involved in web 
based applications while it not applicable for Client 
server applications.

method means ??????????????


Functionality and User Interface Testing can be conducted

Specification-Login screen.
1) Go to User Id field and without entring data in that 
field
Press "Enter" key.
	it should prompt message “Please enter 'User ID' "
Go to login screen enter "User Id"  and without entering

Password try to click on "OK" button.
  	it should prompt message "Please enter 'Password' "

Go to login screen enter "User Id"  and enter wrong
Password try to click on "OK" button.
	it should prompt message " Please enter Proper User 
ID' and  'Password' "
      
Go to Login screen enter all required data and press "OK"
Button then software window will open. In that window click
On "Back" button.
	It should go back to 'Login' screen and that    
Screen should not show "User Id" and "Password"

Go to login screen enter "User Id"  and enter password as
 "god12" try to click on "OK" button.
	It should prompt message for wrong Password.

 Enter valid username with 10 characters and with 
Out enter password and click on ?OK?	Error message r: 
please enter password

Enter password only with 6 characters and click 
On ? OK?	Error message r: please enter username
Enter username with special characters and enter 
Password with special characters and click on ?OK?
		Please enter valid username and password 
without 
Special characters
Enter username with 16 characters and enter 
Password as 6 characters and click on? OK?	
	Please enter below 15 characters for username
Enter username as 12 characters and enter password 
as 3 characters and click on ?OK?	
	Please enter min 5 characters for password

Simply, User authentication testing. This is a part of 
security testing.