LET's LINKED <-> IN

Search This Blog

Sunday, September 9, 2012

Testing Mindz- Delivering Mindz


http://chennai.quikr.com/Testing-Mindz-a-professionally-run-Software-Consultancy-firm-formed-by-W0QQAdIdZ92703710

Thursday, December 1, 2011

Handling Pressure --- Cool it in Mahi Style

Handling Pressure is an art in itself. Actually Pressue is something that you feel. It is relatively proportional to the task and your can do stimulus.The greater the need and the more doubt you have about your ability to do the task the pressure. Because Pressure is internally generated you have the power to manage it yourself,but first you must find the source of the pressure and then figure out how to deal with it. The apparent source of pressure in software projects is the need to meet a tight schedule. This schedule could come form management,your leads and your peers. But the real soure of pressure however,is ourselves.It comes from our natural desire to achieve what our managers or peers want.When this ablity is coupled with normal doubts in oneselves about abilty to accomplish & to perform the results can be destructive.

So,what can be the solutions for this is through a strategy and planning process and show the teams on how to handle pressures.To achieve this we need to start analyze the job,devise a strategy for doing the work,estimate the sizes of the products they will build and then make a plan.

Because unrealistic schedules are the principal cause of software projects problems,helps team manage their projects more effectively. When they are able to manage their work,teams are much more likely to do a quality job.

Tuesday, November 29, 2011

Testing Time -- The Panic Button is On...

Hi All,

Why are you getting panic during our interview session? This thought has been going on in my mind for so long. WE learn so many things & are qualified well enough. But when we are told today you have an interview why are getting into the mood of remorse & panic stricken mood. The emergency button is switched on. Why is this happening? Is it because we have the fear of elimination or we think we don't anything. I used to think so many times in this 45 minutes or an hour and asking few questions what will know about an individual and skills. It is very true but that 45 minutes is also your testing time as you may also not know much about the company except what others tell about the company. So let's make things straight.

When you are called for an interview prepare well on areas where you feel you need improvement & focus on those where you the best. Before the interview read through your CV/Resume well (as most ask questions on your CV only. Go through the company website (if any available)find out from our known sources on the company and be clear for what role you have applied & called for. During the course of interview jus stay calm and answer the questions to the point if you don't either say you don't know or try to give the best answer you are aware of as that give help the interviee to know more about your technical skills.

Its your world... Its your Life... Just go for it...

You have Miles to go before you sleep...

...........All the Best.........

..........Our Life it too wonderful to be spent worrying........

Saturday, May 28, 2011

Deliver your Goods/Words

Hi all,

Its been a gr8 experience in New Jersey. Life is looking good after a longtime. The role of a Delivery Manager is indeed giving a whole new experience in my career.Smoothing the delivery happens only when you are able to understand the requirements of the project and people. If that is clear then the whole idea of delivery is easier. Am learning that.Things are lot better than what it was before.
Both my company and my client is giving a lot towards learning.Its interesting.

God Bless all...:)

Wednesday, March 2, 2011

My Passion to Work for AJ has come to true...:)

At Last....Made it at Last ... My Passion to Work to for this AJ has come true... Now the real game starts...my experience...AJ's rich knowledge...Wow iam excited... to see some real fun...to go on....:)

Saturday, October 9, 2010

We Ranked #24

Hi All,

Thanks to all of you for your continous Support. This Blog is now Ranked #24. It is comingup in the Ladder.Thanks to all of you out there for supporting me & I would like to thanks IndiBlogger.in for showing patience & spending time in evaluting my blog constantly.

Automation Frame Works

FrameWork

What is this all about? Why do we need it?. I had this question in my mind so asked my friend no reply from him. This gave me the idea of exploring more into this topic of Automation Framework.

So I went through quite a lot books & websites to arrive at some definition on this.

So here we go


A FrameWork is nothing but a very organised way of putting your scripts into one place.Framework u can run ur scripts much structured manner.It is very useful in handling Automation Scripts. The design of the Framework varies from Company to company. But there are quite a few that are available which you can use for your automation.

IBM Says " A test automation framework is a set of assumptions, concepts, and practices that provide support for automated software testing"


Lets Start Digging :

A Basic Automation involves a very basic skill of recording & Playback. Through this method. You just have to Open the application along with Automation Tool and Click on the Start Button. There you go all the actions you make on the system gets recorded.This is a very basic way of using any Automation Tool.

Mistakes Made During Record:

1. Before you start recording your application please minimize/close all the other application.I made this mistake so sharing it.It is important that we record only actions for the applications else it is very difficult for us get our results right.

2. Plan well before you make any moves on Automating any application. Plan on how to record , Plan on how you are going to use the datas & populate a value from databases,arranging of your databases.

3. Plan on how your going to arrive at Test Results.

4. Plan on your Frameworks. Decide before you start as to what is suitable & why it is.

5. Guide a Person well if you are trained person. As Novice may our of interest will start recording in the manner her understands but he may come up with results which may need changes.So had you guided him initially he will come up with better results so will be your plans.

Assumptions of Record/Playback

The makers of test automation tool sell/market their product with the ability to capture the user actions and later to playback them. The basic idea of how a GUI-based automated testing works is by its Record/Playback method which is also called as Capture/Replay approach.

The basic of Record/Playback is:

1. Design a test case in the test management tool.

2. Using the Capture Feature you can using the capture feature & record the user actions. What you get is a macro-like script where each user action is presented.You Enhance the recorded script according to your requirement for that you should be aware of a VB Script (mostly used in all the Automation Tool)for you to synchornise it different scripts.

3. Playback the scripts and observe the results in the log of the test management tool.

The basic disadvantage with this method is that

1.You need to keep changing it according to the changes of your,this method contains hard-corded values which if changed frequently involves cost. The Cost are indeed very high & are unacceptable. We use automation tool for reducing our cost in man-power & for other reducution in cost but if this is not possible then there is no point in going for an automation tool , we are happy with manual testing.

2.These scripts are not reliable, even if the application has not changed, and often fail on replay (pop-up windows, messages, and other things can happen that did not happen when the test was recorded).

3.If the tester makes an error entering data, etc., the test must be re-recorded. If the application changes the test must be re-recorded. All that is being tested are things that already work. Areas that have errors are encountered in the recording process (which is manual testing, after all). These bugs are reported, but a script cannot be recorded until the software is corrected. So logically nothing is tested by this approach.

So, it is better we avoid using "Record/Playback" as a method of automating testing. This method is filled with problems and is the time consuming which is costly of all methods over the long term.
It can be used only for determining how the tool is trying to process or interact with the application under test, and can give us some ideas about how to develop your test scripts, but beyond that, its usefulness ends quickly.

There are quite useful Automation FrameWorks available are as follows,

Test Script Modularity
Test Library Architecture
Data-Driven Testing
Keyword-Driven or Table-Driven Testing
Hybrid Test Automation

I hope you all have found this article useful & interesting. Thanks for your time.