Best way to write test case is to categorize them such that it can be applied to the given situation. For instance, if I take an example of ‘Lift aka Elevators‘ then what all tests we can actually perform on lift could be like this: Continue reading “How to test ‘elevators’?”→
In continuation with my last blog I will here share a more advanced capability of Selenium Builder.
Now as we are done with the set up we can talk one step ahead. Lets start with an example :
I have opened a website in firefox and I want to automate some actions on this page . Lets say :
If you have a product mindset and worked with Agile team, you will definitely feel connected with the problem statement I am going to share today.
Yeah, generally we have very few options when this question comes up to a tester while sending a test report to the team. It happens to me often, when a file a bug in some bug tracking tool like JIRA, Microsoft Test Manager, etc, and the worst part is to convince some other person for the bug that I have reported.
there is a web site that takes a load of data and while executing tests,
general user interface testing, I found an issue which is halting me to log into the system.
So the problem statement is quite complicated, I understand, but it is very common.
In continuation of my last post where I discussed what are the roles of the teams in the Agile process, here I am going to discuss how agile help in software development. Also how to actually start with agile software development.
The process focuses that there should be continuous interaction between team members. There are several terms which one should know before getting the knowledge of the process.
Sprint This is an iteration wherein all development, testing, discussions happen. It is of fixed time like 1 week, 2 weeks, 3weeks, etc. It has a specific goal to achieve that depends on the scope of sprint.
Backlog This has all the stories that are to be included in the future sprints or releases.
Sprint Story, This is a TO-DO task with specific business value, with a clear scope. Each story has some end functionality and feature.
Sprint Tasks Each story is further divided into small tasks. These tasks can be of any number and format.
Story point Each story is calculated depending upon its complexity, time is taken to do it, etc, And this is added to each story as a story point of it. Story points are always given to stories in the Fibonacci series pattern, 0,1,1,2,3,5,8,…
Sprint velocity For each Sprint a total calculation of story points as a whole determines the velocity of that Sprint.
This process has to drive by various meetings, let’s discuss them.
All the stories are traversed in the backlog and some stories according to the priorities of stories are taken into consideration. Here all team member estimates the stories and gives story points to each story.
Sprint — Daily stand-ups
In this each team member has to state three details of them :
What he/she has done yesterday
What he is planning to do
What is he doing? Or any blocker if he/she is facing any.
Scrum of scrums
In this, each team’s Scrum Master collaborates to get an update of each team.
This is the demonstration part where each team shows the work they have done within this sprint. It takes place at the end of each sprint.
This is the open space where the team talks on 3 areas:
This happens after the Sprint Retrospective and before the demo of the next sprint.
This is a process in which we can directly call BA within and outside the team, We can manage frequent calls to PO for a better understanding of the product . We can pair with User Acceptance Team for testing and thinking bigger as a customer perspective.
So all in all, unlike traditional models this approach has more interaction, more teamwork, a closer picture of the end product, and a lot more.
I have seen many people asking a repetitive question in interviews if they see Selenium written on any Curriculum Vitae of a Test Engineer. Though I believe theoretical and conceptual knowledge is equally important as hand-on experience. As a part of hiring panel I have observed this as a pet question of our hiring team : ‘How about the architectural difference between Selenium versions.’ Of-course , once they are done with questions like ‘What you know all about selenium’ ?
Selenium generally comes in four different flavours :
Selenium IDE , Selenium RC , Selenium Grid and Selenium Webdriver.
I will be sharing the best answer I got and the research which I did so as to understand the architecture of selenium. Continue reading “Selenium flavors and their architectural differences.”→
If we talk in simple terms Cookies are some thing which parents always teach their child ‘Not to have’.
And same applies to some web sites .They can make life tougher of user when cookies are hiding in the web pages and no one can understand ‘what the heck is making my web page to react so weird!!!’
Let me first start why cookies are required and why/ when are not required. There are several types of cookies (of course not chocolate , strawberry , butter ,etc ) which can comes and lives on the web.
For an example, if I want to log into a system and want to stay in the system for ever until I explicitly log out from it , then to maintain this session go live I always requires some sort of cookies which will make this happen for me. This you can count as an advantage , with out a doubt !
But what about this , when I am working on a web page and trying to search for some one and it will navigate me to some stranger’s profile which has no connection with the name i searched for . It is all about the game which cookies does for us 🙂
Cracking an interview is not a Rocket Science to be frank , but yes for some it could be 😀
Lets talk in general , what is the expectation of an interviewer from an interviewee. Interviewer just want the best answer which is unique and different from the rest of the world. Err…What does that mean ?
For each answer there should be an approach which a tester should mention while answering any question. And that is Always Start With Positive approach .!! Be it writing test cases , or reading requirements , executing test cases , thinking of a scenario in testing ,etc
Lets discuss how can we take an approach of writing test cases with an example which is asked in almost all QA – interviews.
Den her Romeo bløder
Men du kan ikke se hans blod
Det her er kun følelser
Som denne gamle hund gravede op
Ce Roméo saigne
Mais on ne peut voir son sang
Ce ne sont rien d’autre que quelques sentiments
Que ce vieux chien a réveillé
Bu Romeo kanıyor
Ama kanını göremezsiniz
Bazı duygulardan fazlası değildir
Bu yaşlı köpeğin tekmelediği
Nice song , yeah !!!
Which one of the above translation you find easy to understand. And how you can actually make this understand to all other unheralded persons who does not know ‘Always’ song or Bon Jovi for that matter.
The answer is you will translate the same in to a common language which everyone can understand like ‘English’ in a similar manner like this :
This Romeo is bleeding
But you can’t see his blood
It’s nothing but some feelings
That this old dog kicked up
In agile methodology, when we talk about delivery then its all about the customer satisfaction and acceptance. Recently, I presented a session in an open forum stating what Behavior-driven development (BDD) can actually do and how can we start applying BDD in our day-to-day development.
BDD is an interface between a coder and a customer. It turns a requirement into a simplified language, which everyone can understand and then in the backend the required work is done.
Generally, the requirements are not clear initially and then the costs incurred to add changes are more in the long run, say, at the time of delivery. The best part of this technique is that we can bridge the gap and have a common understanding of the Definition Of Done between all; coder, quality analyst , customer, end user, business analysts. This applies to each and every person who are involved in the software development process right from the initial days to the delivery of the product.
The current trend in user interfaces is geared towards graphical user interfaces (GUIs). GUIs are very complicated and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a forthright task. Automation is not that easy at first.
I agree , Software development comes with different flavors but the whole idea is to make a Working Model out of some technical skills and some some creative ideas.
In continuation , Testing in general is what we used to do on daily basis .
For example , if we are going to buy a mobile phone then generally what we used to see in any hand set is what color is most appealing , is the phone handy , is the hand set worth taking in comparison to its price , if i ll start the phone what all specifications i will get , what kind of camera it has , what all NEW features it has , what is the unique thing which is making it different from rest of the phone of different brand having same features but different range , etc etc..