There are multiple approaches you can take to kick start mobile testing. For this you need to understand what you are actually trying to achieve and what constraints you have like how many team members, testing devices, etc.
The first thing you have to have a good environment to start with. There are two ways to do the same one via emulators, and the other on actual devices. Emulators are easily available, free of cost though they are very slow and real results are hard to capture in them. While real devices are fast which lead to real results and are easy to use. Continue reading “How to start mobile testing in android.”→
During my experience in testing, I have worked on multiple databases, and I must say if you are working on database direct interaction then you must have encountered issues now and then over various areas.
One of the major issue is when you are dealing with databases having multiple tables and these tables are connected with each other with constraints like foreign keys, primary keys, triggers, stored procedures etc.
Other being, when a database server is used by various team members then you might see issue related to concurrent users. Today in this piece of write-up I will share how can we deal with multiple databases when multiple user is using one database server. In other words, how can we drop the connections in different databases, how can we make it happen via scripts like Shell scripts, etc. Continue reading “How to deal with the databases when it stops following its own master.”→
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.”→
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.
Often, Recording and playing back a recorded script using Selenium IDE and Webdriver is just a stepping stone to write a more meaningful test script(see my last blog). Almost, in all the cases, it serves as a template to add more code and to do more.
At times there are many facts which we used to overlook which seems very minute but turns to be very weird when comes to actual writing. While it may be a straight thing to use a locator strategy suggested by the recorded test, this is seldom useful while dealing with dynamic resources. One of them is finding locators.
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..
In today’s fast paced world, the task of manual testing where huge amounts of data is involved looks very cumbersome. Time is like the wind, it lifts the light and leaves the heavy. We have so little time to get all the things done which we want to do in our busy lives. This really comes into picture when it comes to running your own online business or site.
Many, perchance most, software applications today are written as web-based applications to be run in an Internet browser. The efficacy of testing these applications varies broadly amid-st companies and organizations. In an era of highly interactive and susceptible software processes where many organizations are using some form of Agile methodology, test automation is frequently becoming a exigency for software projects. Test automation is oftentimes the answer. Test automation means using a software tool to run repeatable tests against the application to be tested.