Agile Testing would most obviously apply to agile development projects, but it will less work on conventional project.
 
In Conventional projects others communicate at us with requirements and design documents, and we bring out with test plans and bug reports. We've always realized that the documents we base our tests on are flawed - incomplete, incorrect, and ambiguous - but our reaction has been to insist, in our usually powerless way, that the document producers do better. But now we can see that "better" will never be good enough. So In agile environment Tester and developers will work together, sit in the same bullpen, share offices, or occupy alternate cubicles. Many testers should be assigned to help particular developers, rather than to test pieces of the product. The test plan should evolve through a series of "drop-in meetings" - short, low-preparation, informal discussions of particular topics. These will result in "test doclets" - short memos addressing a specific issue.
 
Let me give you how exactly agile methodology work I hope this will get clear picture how agile testing goes.
 
A software method is Agile when development is incremental (small software releases with rapid cycles), cooperative, straightforward (the processes are easy to learn and to modify) and adaptive (able to make last minute changes).
 
Iterative Development
Project is structured as multiple short cycles in sequence, versus one long cycle.
 
Incremental Development
Each iteration produces a usable increment of finished product, with actual customer value.
 
Testing activities starts from requirement analysis and goes throughout the lifecycle. During Iteration 0, we might perform initial setup tasks. The good news is that we'll discover that increased testing during construction iterations enables us to do less testing during the End Game. In due course we will have Rapid Releases, Changing Requirements, Late Requirements, Early insight, reviews.Agile will not believe in heavy documentation. We will have User story’s instead of requirement specifications.
 
In agile, iteration are called as sprints-1, sprint-2, each sprint has one month duration. Product owner, stake holders and team members will sit together and identifies the features can be developed for that sprint. In agile team members will specify the actually time/Man hours to develop the feature where is has to work whether it is a development or testing (test case development and testing case execution).
 
By considering all the team members data team manager will bring out Burn down chart for that sprint. It may possible that some features are taking more time or there may be dependence's, so that feature may go to Product Back log/sprint Back log. It will be taken up in the next sprints.
 
In duration of sprint period we will have Daily stand up Scrum meeting where all the team members will discuss what he/she did in last -24 hrs and what he is going to do in coming +24 hrs, apart from this he/she going to discuss any obstacle the for him/her to complete that task. Each member will allocate 3-5 mins time in the meeting. If there is need for technical discuss then it will carry out after the scrum meeting. There will be a scrum master who will be going to note down each point in scrum meeting.
 
At the end of sprint we will have sprint meeting, where all the team members are going to discuss what gone well, what not gone well in this sprint and all team members will come up with suggestion/changes for the future sprints.
 
Agile Testing is not the answer for all projects. But now is a time when we need more experimentation with project styles, the more so because there's an increasing move toward standardization of software development practices.