Blog

Latest Updates. News. Insights. Ideas.

Ajay Balamurugadas, Author at Sahi Pro

Test Talks: Automation Awesomeness: Test Automation Using Sahi with Narayan Raman

Posted by | Agile, marketing, People, Speakers, talks, web automation | No Comments

Our CEO Mr. Narayan Raman was featured on Joe Colantonio’s Test Talks. Listen to the Test Talk to discover why Sahi Pro might be the right choice and the parameters to consider while choosing a test automation tool, apart from other insights on Sahi Pro and Sahi Open Source.

135: Test Automation Using Sahi with Narayan Raman

Quotes & Insights from this Test Talk

  • Created Sahi After Attempt at Agile Needed something more lightweight and easier to use. Developers and browsers were moving too fast
  • Very tester-focused, an effort to make it easier for a nyone to automate applications. Many testers are not programmers, and Sahi helps them understand the basics. Most testing code is procedural; you take steps and you verify results. Sahi helps to keep it simple! Organize functions into the right files Make sure you’re calling the right parameters
  • This tool is good for both testers and developers. Developers write the application as it should function; the automation team and the tester team should be able to work with a working application, and be able to automate it; they should no thave anything extra done for that automation. If the tool requires more, there’s going to be pushback from developers. The end tester should know about only the actions he performs on the
  • Example: “Recording a sequence for playback is considered a tricky task on most web applications,” but this was fairly successful. Helped testers to quickly automate the app and script it took tester through 30% or 40% of initial automation phase. After that, you should be refactoring the code into functions and have reusable libraries
  • Sahi’s Recorder, and being able to work more closely with the browser, helped make the testing process faster. Record and Playback records image in Javascript. There’s also a Java Recorder
    Sahi vs Selenium (both came out around the same time)
    * Premises
    – “ Selenium was built on the premise that the developer himself would also write every test for everything that he builds; he has full control over the application that he’s testing.”
    – In Sahi, the end tester does not need to know too much about the app. If there is something he needs to automate, he does not need to go back to the developer all the time.
    – Operations
    – Selenium uses XPath, CSS Selectors, Waits, etc
    – Sahi handles a lot of complexity internally
    – enters Javascript into web page
    – Hooks into XMLHTTPRequestObject, and wait until AJAX activity
    has subsided on the page before proceeding to execute a step
    – Eliminates need for implicit or explicit waits
    – “Any element of interest to automation will always have something by
    which it can be identified, even if it doesn’t have an ID…Depending on the
    kind of element, we have a sequence of attributes by which we try to
    identify that element… the code automatically iterates to the frame and
    finds the element.”
    – “XPath is a strict no-no in Sahi.”
    – Does not rely on structure of HTML page to ID elements
    – Makes elements more stable
    – Sahi is similar to Selenium IDE, but it will work on any browser
    – Recorder will carry over between browsers, as well
    – Finds most useful attribute value during recording phase, and stores that one only
    – Eventually, triggers will come from a continuous integration system
  • Sahi Pro ( www.sahipro.com )
    – Adds enterprise features to Sahi
    – Better for bigger organizations with larger suites
    – Helps test automation team focus on the automation itself
    – Distribution across multiple machines
    – Test suite executed across all machines
    – Pull reports and generate one consolidated report
    – Can be stored in a database
    – Puts system reports in database
    – Reports are more varied and configurable
    – Historic overview available for test suite
    – Can analyze trends and patterns
    – Log reports
    – Screenshots
  • When choosing tools or trying to automate, think what is important for the business, and not what is important for a resume review. What adds the most business value is what is going to take you higher in your organization, and also is going to help the business that you’re actually employed with.

Feel free to request a demo and check out if your automation challenges can be solved using Sahi Pro.

Know your TestBash Speakers: Elizabeth Zagroba

Posted by | Conferences, Speakers, TestBash Philadelphia | No Comments

This series of blog posts is an attempt to introduce you to some of the TestBash Philadelphia 2016 speakers and ask them few questions related to the talk/work. Our previous speakers interviews can be read here: Alan Page, Maaret Pyhäjärvi, Dan Ashby and Stephen JanawayNancy Kelln and Angie Jones.

Today, we introduce you to Elizabeth Zagroba. For those who have not heard of Elizabeth, here is a brief introduction about her from the speakers page at TestBash Philadelphia 2016.

Elizabeth Zagroba is a context-driven software tester at Huge in Brooklyn. She’s tested innovative user interfaces for iOS and Android apps, responsive websites, content management systems, and streaming and on-demand audio. Before Huge, Elizabeth worked on the digital team at a public radio station in Manhattan.

Her session is titled: Succeeding as an Introvert

Sahi Pro: When do introverts give their best?
Elizabeth:
Introverts give their best when they have time on their own to prepare. Introverts process information more deeply and make more connections, but that can take longer. Brainstorming sessions, meetings without an agenda, or putting people on the spot won’t get the best out of an introvert.

Sahi Pro: What are few misconceptions about introverts?
Elizabeth: 
I think the biggest misconception about introverts is that they’re just shy. Shyness is a social anxiety that stops people from doing the things they want to do: chairing the committee, speaking up. Introverts don’t want to be doing those things in the first place. I think introverts can also be seen as boring or not knowing how to have fun. Introverts recharge when they’re alone, so they might be less eager to go out for lunch or a drink after work.

Sahi Pro: “Innovative user interfaces for iOS and Android apps”, Sounds interesting, tell us more.
Elizabeth: 
I love working on projects where the expected behavior is unknown. I worked on the Radiolab app at New York Public Radio. The show is an immersive sound and psychological experience, so we tried to mirror that in the app. The navigation travelled from a room, to a field outside, and up into space, with stops along the way for different pieces of information and Easter eggs. At Huge, I worked on an app for EA Sports that took a 3D scan of your face so you could play alongside your favorite basketball players in the NBA Live 2016 video game. With the camera activated, you held your phone in place and turned your head from side to side. In both apps, the onboarding and coaching was the most important part. We wanted people to use their devices in ways they weren’t expecting. I enjoyed figuring out what people assumed and finding ways to reorient them.

Thank you for your time, Elizabeth Zagroba. We appreciate your contribution to the software community and best wishes to you and the conference.

Hope everyone has a good time, listening to Elizabeth speak on “Succeeding as an Introvert” session. Do tweet and blog about the conference and share the learning with the software community.

About Sahi Pro:
We  are one of the micro sponsors of TestBash Philadelphia 2016.

Sahi Pro, the flagship product of Tyto Software, is a simple yet powerful test automation tool that enables Quality Assurance and Testing teams achieve high efficiency and productivity in their test automation
process. Features like multi browser support, good recorder, automatic waits, inbuilt frameworks, and automatic reporting reduce the team’s effort and technical expertise required, ensuring faster delivery cycles, especially in Agile environments. Over 400 enterprise customers across diverse industry verticals like Banking and Financial Services, Healthcare, IT Services, IT Products, Retail, Media & Entertainment, Telecom and Government are achieving high ROI with Sahi Pro.

Visit sahipro.com or connect with us on Facebook, Twitter or LinkedIn

Know your TestBash Speakers: Angie Jones

Posted by | Conferences, Speakers, TestBash Philadelphia | No Comments

This series of blog posts is an attempt to introduce you to some of the TestBash Philadelphia 2016 speakers and ask them few questions related to the talk/work. Our previous speakers interviews can be read here: Alan Page, Maaret Pyhäjärvi, Dan Ashby and Stephen Janaway and Nancy Kelln.

Today, we introduce you to Angie Jones. For those who have not heard of Angie, here is a brief introduction about her from the speakers page at TestBash Philadelphia 2016.

Angie Jones is a Consulting Automation Engineer at LexisNexis. Angie advises several scrum teams on QA Automation strategies and best practices and has developed automation frameworks for countless software products. Angie is known for her innovative and out-of-the-box thinking style which has resulted in more than 20 patented inventions in the US and China. Angie is also an Adjunct Instructor of Computer Programming at Durham Technical Community College. Angie is a strong advocate for diversity in Technology and volunteers with organizations who champion this cause such as TechGirlz and Black Girls Code. She can be found on Twitter at @techgirl1908.

Her session is titled: How to Get Automation Included in Your Definition of Done

Sahi Pro: How do you use automation to assist testing activities?
Angie Jones: 
As quality initiatives are shifting left, long extensive regression testing periods are a thing of the past. I automate scenarios so that not only are they covered during scheduled regression testing windows, but they are also run on a continuous basis – every time there is a development change in the code. This frees testers up to focus on new tests, exploration, and more complex user journeys. It also gives developers fast feedback about the state of the system after the deployment of their changes.

Sahi Pro: What kind of problems do you face trying to automate the regression tests in organizations?
Angie Jones: 
The biggest challenge is probably not the coding itself, but educating and convincing others of what the purpose of automation is. It’s very typical for managers and executives to want to automate everything. I don’t feel this is the right approach. One reason is because the return on investment (ROI) is not always great enough to warrant automation of every single scenario. A lot of times, businesses get caught up on numbers instead of focusing on ensuring their teams are automating the right things.

Sahi Pro: What is your first question to anyone who wants to use automation in their organization?
Angie Jones: 
Who will lead your automation strategy? This is so very critical, as it often determines whether an automation effort will succeed or fail.
Sometimes managers or executives try to lay the entire strategy out themselves with a very basic high-level understanding of automation. They then hire people to implement their flawed strategy, ultimately resulting in a flawed solution that is destined to fail.
Fortunately, I have only encountered a few organizations like that. But many managers, still try to work with what they have, so they entrust a developer or a tester to lead the automation strategy. This also is not ideal, as the developer may lack the testing mindset and in-depth knowledge of practical automation practices; and the tester may lack the technical skills to be able to architect a sustainable automation solution.
I encourage organizations to invest in an automation engineer – someone who is a hybrid of developer and tester and who has experience in building automation solutions. Sometimes, an org lucks up and has a manager, developer, or tester who either used to be an automation engineer, or currently studies the craft very closely. In cases like those, these people can definitely be successful in leading the strategy.

Thank you for your time, Angie Jones. We appreciate your contribution to the software community and best wishes to you and the conference.

Hope everyone has a good time, listening to Angie speak on “How to Get Automation Included in Your Definition of Done” session. Do tweet and blog about the conference and share the learning with the software community.

About Sahi Pro:
We  are one of the micro sponsors of TestBash Philadelphia 2016.

Sahi Pro, the flagship product of Tyto Software, is a simple yet powerful test automation tool that enables Quality Assurance and Testing teams achieve high efficiency and productivity in their test automation
process. Features like multi browser support, good recorder, automatic waits, inbuilt frameworks, and automatic reporting reduce the team’s effort and technical expertise required, ensuring faster delivery cycles, especially in Agile environments. Over 400 enterprise customers across diverse industry verticals like Banking and Financial Services, Healthcare, IT Services, IT Products, Retail, Media & Entertainment, Telecom and Government are achieving high ROI with Sahi Pro.

Visit sahipro.com or connect with us on Facebook, Twitter or LinkedIn

Know your TestBash Speakers: Nancy Kelln

Posted by | Conferences, Speakers, TestBash Philadelphia | No Comments

This series of blog posts is an attempt to introduce you to some of the TestBash Philadelphia 2016 speakers and ask them few questions related to the talk/work. Our previous speakers interviews can be read here: Alan Page, Maaret Pyhäjärvi, Dan Ashby and Stephen Janaway.

Today, we introduce you to Nancy Kelln. For those who have not heard of Nancy, here is a brief introduction about them from the speakers page at TestBash Philadelphia 2016.

Test Manager at FGL Sports Ltd. with 16 years of diverse IT experience, Nancy enjoys working with teams that are implementing or enhancing their testing practices and provides adaptive testing approaches to both exploratory and traditional testing teams. She has coached test teams in various environments and facilitated numerous local and international workshops and presentations. From small scale to multi-million dollar projects; Nancy has played many roles within testing including Project Test Manager, Test Manager, Test Lead and Tester. A co-founder of POST, Nancy is an active member of the Calgary Software Quality Discussion Group, Association for Software Testing, and the Software Test Professionals organization. Nancy and her family live in Airdrie, Alberta, Canada. Connect with Nancy on Twitter @nkelln.

Her session is titled: What the Hell Kind of Testing is That?

Sahi Pro: What is the biggest resistance when you try to implement ET (Exploratory Testing) in most of the organizations?
Nancy: 
The biggest resistance when implementing ET in organizations has been gaining alignment and dealing with other people’s fear. Organizations will say they want change. The leaders, and
managers and employees will all nod their heads and wholeheartedly agree that ‘change needs to happen’ and some will even go out and start making that change. But even with agreement,
many organizations and the people within them fear change. Even though they see things are broken and need changing they fear the unknown that change can bring. They worry that things
will get worse (before they get better) and that their current ways of coping with the broken aspects of the system will no longer work, leaving them with more problems, roadblocks or delays that they no longer the means to deal with.

Sahi Pro: How did the community respond to your tweet to chat about the challenges in implementing ET?
Nancy: 
Testers LOVE to talk about testing. I received an amazing number of responses from my twitter request. It gave me some great ideas to include for the TestBash session as well as fueled my fire for a workshop on Implementing ET in Organizations that I am currently putting together.

SahiPro: Any organizations that you admire for how they approach testing?
Nancy:
I don’t believe organizations drive testing so there isn’t an organization I would say I admire. What I do admire are the testers who are advocating for testing in their organization. The ones that are passionate about testing and have proclaimed that testing is their career. The ones that are mentoring others in their companies, either formally or informally, about good testing practices. The ones who aren’t afraid to try something new, push the envelop and raise the bar with their own testing and assist others in doing the same. The ones blogging and speaking and challenging testing ideas while bringing new ideas for others to consider. These are the people that drive the testing direction for organizations and change the way organizations implement testing.

Thank you for your time, Nancy. We appreciate your contribution to the software community and best wishes to you and the conference.

Hope everyone has a good time, listening to Nancy speak on “What the Hell Kind of Testing is That?” session. Do tweet and blog about the conference and share the learning with the software community.

About Sahi Pro:
We  are one of the micro sponsors of TestBash Philadelphia 2016.

Sahi Pro, the flagship product of Tyto Software, is a simple yet powerful test automation tool that enables Quality Assurance and Testing teams achieve high efficiency and productivity in their test automation
process. Features like multi browser support, good recorder, automatic waits, inbuilt frameworks, and automatic reporting reduce the team’s effort and technical expertise required, ensuring faster delivery cycles, especially in Agile environments. Over 400 enterprise customers across diverse industry verticals like Banking and Financial Services, Healthcare, IT Services, IT Products, Retail, Media & Entertainment, Telecom and Government are achieving high ROI with Sahi Pro.

Visit sahipro.com or connect with us on Facebook, Twitter or LinkedIn

Know your TestBash Speakers: Dan Ashby and Stephen Janaway

Posted by | Conferences, Speakers, TestBash Philadelphia | No Comments

testbashphilly

This series of blog posts is an attempt to introduce you to some of the TestBash Philadelphia 2016 speakers and ask them few questions related to the talk/work. Our previous speakers interviews can be read here: Alan Page and Maaret Pyhäjärvi.

Today, we introduce you to Dan Ashby and Stephen Janaway. For those who have not heard of Dan and Stephen, here is a brief introduction about them from the speakers page at TestBash Philadelphia 2016.

Dan Ashby has been a Software Tester for almost a decade now, testing a wide range of products from PC drivers, to printer software/hardware/firmware, to web apps and websites of all different sizes. He has a passion for Exploratory Testing with a focus on testing web-based applications and web sites. Find him on Twitter at @danashby04.

Stephen is a mobile and e-commerce Coach, Strategist and Manager. Over the last 15 years he’s worked for companies such as Nokia. Ericsson, Motorola and the YOOX NET-A-PORTER GROUP, as well as advising a number of mobile application companies on testing and delivery strategies. He has written and presented many times about testing, frequently with a focus on mobile devices and mobile applications. Stephen loves talking to others about software testing, test techniques and the mobile device and application world in general. You can contact him via his website (www.stephenjanaway.co.uk) or on Twitter (@stephenjanaway).

Their session is titled: Giving Something Back ­- Testing In The Pub ­ Live! 

Sahi Pro: Congratulations on 25+ podcasts. What has been your biggest learning?
Dan & Stephen: 
Thanks 🙂 We’re at number 37 now – it’s been a great learning exercise. The biggest thing that we’ve learnt from doing the podcast is that you can start something small and let it grow organically. Testing In The Pub started because we used to work in the same company and would sit and talk about testing over a cup of tea. One day we thought “why not record this?”; I’d been listen to A/B Testing a fair bit which Alan Page and Brent Jensen do a great job on and so it seemed logical. By starting small then we had the opportunity to do something that was simple and less time consuming to experiment with. It’s also been great to discover that lots of people want to be a part of the podcast and indicative of the open and welcoming nature of the software testing community.

Sahi Pro: How do you decide on whom to have in the next podcast?
Dan & Stephen:
It depends on a number of factors. We have some people that we plan to record with, and therefore need to organise sessions with, particularly if they are well known and busy. In other cases it’s dependant on where we are – we record at a lot at conferences and find that we can get some great discussions going simply by seeing who’s around in the bar or at the breaks. It’s fair to say that there’s no grand plan and that’s how it should be since it allows us to record episodes that react to the current thinking in the community.

Sahi Pro: What motivates you to contribute to the community considering that releasing a podcast regularly is not an easy task.
Dan & Stephen:
Communities die if people don’t contribute to them and we both feel really strongly that if one takes from the community then there’s an obligation to give something back. We’ve both learnt a lot from the testing community and continue to do so, and we’ve had a lot of fun as we do, so it would not be right to just take. Testing In The Pub is one example, together with the speaking we both do at conferences and also the Software Testing Clinic that Dan helps runs in London. Also doing Testing In The Pub is a whole lot of fun; it does take time to do but if one is enjoying something then it’s usually worth doing in my experience. 

TESTING IN THE PUB – YOUR REGULAR PODCAST ALL ABOUT SOFTWARE TESTING
Listen to Steve and Dan talk about topics of interest, and sometimes interview leading members of the software testing community too.
You can subscribe via RSS or iTunes, or stream or download directly from this site.

Thank you for your time, Dan and Stephen. We appreciate your contribution to the software community and best wishes to you and the conference.

Hope everyone has a good time, listening to them engage you with “LIVE Testing In the Pub” session. Do tweet and blog about the conference and share the learning with the software community.

About Sahi Pro:
We  are one of the micro sponsors of TestBash Philadelphia 2016.

Sahi Pro, the flagship product of Tyto Software, is a simple yet powerful test automation tool that enables Quality Assurance and Testing teams achieve high efficiency and productivity in their test automation
process. Features like multi browser support, good recorder, automatic waits, inbuilt frameworks, and automatic reporting reduce the team’s effort and technical expertise required, ensuring faster delivery cycles, especially in Agile environments. Over 400 enterprise customers across diverse industry verticals like Banking and Financial Services, Healthcare, IT Services, IT Products, Retail, Media & Entertainment, Telecom and Government are achieving high ROI with Sahi Pro.

Visit sahipro.com or connect with us on Facebook, Twitter or LinkedIn

DevOps East Conference: Win yourself discounted tickets!!!

Posted by | Conferences, Contests, DevOps East | No Comments

DevOpsEast_Logo

We at Tyto Software (the creators of Sahi Pro) love conferences and contests. Our evangelist is presenting a talk on “Automation in Testing” at the Agile Testing and Test Automation Summit, Bangalore.
We are also the silver sponsors of DevOps East Conference to be held this November 13-18 at Orlando, FL.
You can read more about the conference here. We have got discount codes as part of the sponsorship package. We can also nominate two people to register at discounted rates (which is really cool).

We have come up with a contest to select the two winners who can register at discounted rates.
Every contest participant will receive the discount code (worth $200).

More details about the contest below.

    1. The contest is for only three days October 21 – October 23, 2016.
    2. You need to describe the features of Sahi Pro to the world. It could be a blog post, a YouTube video, a Facebook post or anything that would help anyone understand the features of Sahi Pro. Be creative and take on the role of Sahi Pro Evangelist for these three days.
    3. Share it with us and on social media. The post with the highest shares/likes/retweets by Oct 23,
      6 PM IST
      will be declared as the winner.

We can clearly identify whose post is liked by real people and who has used bots. Judges decision is final.

Any questions, feel free to shoot an email to AJAY[AT]SAHIPRO[DOT]COM with the subject line –
“DevOps – Sahi Pro Contest”

Useful links:

Conference Website: https://devopseast.techwell.com/
Sahi Pro Website: www.sahipro.com
Sahi Pro Documentation: www.sahipro.com/docs

All the participants of this contest will receive a discount code worth $200.

Two winners can register for the Conference and/or Tutorials and/or Leadership Summit at following discounted rates.
> CONFERENCE DELEGATE $ 997.50 $1995
> CONFERENCE DELEGATE WITH 1 TUTORIAL $ 1,197.50 $2395
> CONFERENCE DELEGATE WITH 2 TUTORIALS $ 1,397.50 $2795
> LEADERSHIP SUMMIT $500 $795

Good luck with the contest. Looking forward to receiving your entries at AJAY[AT]SAHIPRO[DOT]COM

Know your TestBash Speakers: Maaret Pyhäjärvi

Posted by | Conferences, Speakers, TestBash Philadelphia | No Comments

testbashphilly

This series of blog posts is an attempt to introduce you to some of the TestBash Philadelphia 2016 speakers and ask them few questions related to the talk/work. Our first speaker was Alan Page. You can read the blog post here.

Today, we introduce you to Maaret Pyhäjärvi. For those who have not heard of Maaret, here is a brief introduction about her from the speakers page at TestBash Philadelphia 2016.

Maaret Pyhäjärvi is a software professional with testing emphasis. Her day job is working with a small software product development team as a hands-on testing specialist, doing continuous delivery with limited test automation. On the side, she teaches exploratory testing and makes a point of adding new, relevant feedback for test-automation heavy projects through skilled exploratory testing. In addition to being a tester and a teacher, she is a serial volunteer for different non-profits driving forward the state of software development. She blogs regularly at http://visible-quality.blogspot.fi and is the author of Mob Programming Guidebook.

Her talk is titled: A Mob Testing Experience

Sahi Pro: How did this idea of mob testing strike you?
Maaret Pyhäjärvi: I heard about mob programming at a conference from Woody Zuill, the discoverer of mob programming. It sounded both ridiculous and interesting, and my team was struggling with collaboration. So we started mob programming together. I paid particular attention to the testing aspects, being worried that the mob and code focus would make me less of a tester, but soon realized it enabled me to fix things from half-a-sentence without developer ego in play, and guide the whole team to understand what it is that I do when I explore an application.

Encouraged by the small successes with my team, I started experimenting with testers in the community, specifically on mob exploratory testing. I had sessions in open space conferences, and learned to facilitate better. And, realized that the connection of participants and my ability to teach in this format really made it a great way of teaching and learning of exploratory testing. Later I also started test automation in mob format, with same results. It’s fun and reveals a lot of the silent knowledge we have that we use to do great testing. No theory tops a hands-on learning experience.

Sahi Pro: What were the initial challenges faced when trying this idea on teams?
Maaret Pyhäjärvi: 
10 people working on one computer sounds like waste – that is the 1st thing to address. We talked about it as an investment to learning, and time boxed it to two hours a week. Keeping it with a learning focus lowers the bar. I still have not gone to the full-time mob experience some companies report on where all their work is done as a group on one computer. We needed to learn to understand that it isn’t about getting the most out everyone, but it’s about getting the best out of everyone into the work we do. With on-time corrections, we could avoid a lot of rework, and saying something relevant just once to fix an error about to happen was valuable.

For me as a tester, the initial challenge was also to overcome my fears. I would be exposed on my lack of interest and practice with the code writing part, and 9 developers could walk over me any time. And some of them were not very nice when working in pairs. I guess the developers felt the same but for different reasons. But it turned out to be a very safe environment to learn together.

Sahi Pro: Any pre-requisites before trying out a similar session at work?
Maaret Pyhäjärvi: Look at the basic dynamics of a practice mob. The first thing to learn is to communicate, so that when you have an idea, you are speaking about it and someone else is on the keyboard. Also, we need to first learn all to share in this format, and having a role of a designated navigator is a great beginning practice to make sure everyone takes their turn on both driver and navigator roles.

It can be a good idea for someone to just step out of the mob and facilitate. Just remind on rules, roles and rotation, and make sure the group retrospects after the experience.

Thank you for your time, Maaret. We appreciate your contribution to the software community and best wishes to you and the conference.

Hope everyone has a good time, listening to Maaret engage you with “A Mob Testing Experience”. Do tweet and blog about the conference and share the learning with the software community.

About Sahi Pro:
We  are one of the micro sponsors of TestBash Philadelphia 2016.

Sahi Pro, the flagship product of Tyto Software, is a simple yet powerful test automation tool that enables Quality Assurance and Testing teams achieve high efficiency and productivity in their test automation
process. Features like multi browser support, good recorder, automatic waits, inbuilt frameworks, and automatic reporting reduce the team’s effort and technical expertise required, ensuring faster delivery cycles, especially in Agile environments. Over 400 enterprise customers across diverse industry verticals like Banking and Financial Services, Healthcare, IT Services, IT Products, Retail, Media & Entertainment, Telecom and Government are achieving high ROI with Sahi Pro.

Visit sahipro.com or connect with us on Facebook, Twitter or LinkedIn

Watch this space to know about our next TestBash speaker… Any guesses? 🙂

Know your TestBash Speakers: Alan Page

Posted by | Conferences, Speakers, TestBash Philadelphia | No Comments

In most of the conferences, you attend the talks by various speakers and then wonder why did you attend some of those talks. At the same time, you also like few speakers and go – “Wow, I think our interests match. Let me have a chat.” This series of blog posts is an attempt to introduce you to some of the TestBash Philadelphia 2016 speakers and ask them few questions related to the talk/work.

testbashphilly

Today, we introduce you to Alan Page. For those who have not heard of Alan, here is a brief introduction about him from the speakers page at TestBash Philadelphia 2016.

Alan Page has been building and testing software for nearly 25 years. He was the lead author on the book How We Test Software at Microsoft, contributed chapters for Beautiful Testing and Experiences of Test Automation: Case Studies of Software Test Automation , and recently published a collection of essays on test automation in The A Word. He also writes about a variety of software engineering subjects on his blog at http://angryweasel.com/blog.

Alan joined Microsoft as a member of the Windows 95 team, and since then has worked on a variety of Windows releases, early versions of Internet Explorer; Office Lync and Xbox One. Alan also served for two years as Microsoft’s Director of Test Excellence. Currently, he’s working on a brand new collaboration application for Microsoft.

His talk is titled: Testing without Testers (and other dumb ideas that sometimes work)

Sahi Pro: Many testers are scared about losing their jobs. What would be your advice to them?
Alan Page: If you are a tester who purely executes functional tests and does little else, you should probably be very worried about losing your job. That kind of testing just isn’t useful or efficient anymore.

However – if you’re a tester who can provide value to the product by finding holes and identifying risk; and you are a tester who can take on testing or quality related (e.g. reporting / data analysis, analysis tools, build / deployment, or other tooling), you will have a long career in software engineering.

Testing is certainly changing, but it’s not quite dead yet. As long as you love to learn and aren’t afraid of taking on new challenges, there’s no reason to be scared.

Sahi Pro: How would you define quality?
Alan Page: 
I’m a fan of the Weinberg definition, but I think it’s over-used these days, so I’ll paraphrase it and dance around it a bit so it doesn’t seem quite so redundant.

To me, quality is the engagement, connection, and use I get from a product. It’s personal – what’s quality to me, may not be quality for you. I have quality knives at home – they are easy to use, I feel comfortable using them, and I miss them if I’m using knives elsewhere. My knives are nice, but they may not provide enough use for you to consider them quality knives.

In software, quality comes from the same criteria. The software I consider to be quality software is software that I use frequently; software that is easy for me to use; and software where I don’t get frustrated – even if there are bugs. As a counter-example, consider that it’s certainly possible to have bug free software that has no value to users – I, for one, would never consider that to be quality software.

Sahi Pro: Congratulations on the 40+ episodes of AB Testing. What was the motivation behind starting this podcast series?
Alan Page:
 Brent and I have known each other for many years. We used to connect every week or so as part of a group of senior testers spanning Microsoft. A small group of us would get together in sort of a lean coffee style every week or two and talk about what was going on in our parts of Microsoft. Brent and I always had a good banter, and we used to threaten to start a podcast so everyone could hear us talk about software.

Eventually, we took the threat public and started the AB Podcast. I can’t believe we’re approaching episode 50 already, but we enjoy doing the podcast, and are both surprised and ecstatic that we have so many listeners.

Podcast link: http://angryweasel.com/.ABTesting
Blog: http://angryweasel.com

Thank you for your time, Alan. We appreciate your contribution to the software community and best wishes to you and the conference.

Hope everyone has a good time, listening to Alan speak about “Testing without Testers (and other dumb ideas that sometimes work)”. Do tweet and blog about the conference and share the learning with the software community.

About Sahi Pro:
We  are one of the micro sponsors of TestBash Philadelphia 2016.

Sahi Pro, the flagship product of Tyto Software, is a simple yet powerful test automation tool that enables Quality Assurance and Testing teams achieve high efficiency and productivity in their test automation
process. Features like multi browser support, good recorder, automatic waits, inbuilt frameworks, and automatic reporting reduce the team’s effort and technical expertise required, ensuring faster delivery cycles, especially in Agile environments. Over 400 enterprise customers across diverse industry verticals like Banking and Financial Services, Healthcare, IT Services, IT Products, Retail, Media & Entertainment, Telecom and Government are achieving high ROI with Sahi Pro.

Visit sahipro.com or connect with us on Facebook, Twitter or LinkedIn

Watch this space to know about our next TestBash speaker… Any guesses? 🙂

Tyto Software (Creators of Sahi Pro) is Proud to Sponsor

Posted by | Agile Testing Days, Conferences, DevOps East, TestBash Philadelphia | No Comments

two (this might increase soon) conferences this year.
We love to interact with the software testing community. Though there are multiple conferences happening at this time of the year, due to time and other constraints, we picked the following conferences to sponsor.

Silver Sponsors
Agile Development, Better Software, & DevOps East Conference
Date: Nov 13–18, 2016
Location: Orlando, FL
Website: https://adceast.techwell.com/

Agile Dev East Conference

Agile Dev East Conference

The conference starts with a full day training class on different roles in Agile teams like ScrumMaster, Agile Tester, Product Owner certification and also on how to integrate test with a DevOps approach. The next two days have a lot of half-day and full-day tutorials.

Tutorial Topics                                                                                                 Tutorial Topics

We also liked how the tracks were classified into eight different themes:
Agile Leadership, Agile Metrics, Agile Requirements
Projects & Teams, Going Mobile, Software Quality
DevOps, DevOps Implementation.

After lunch, the tracks change to
Enterprise Agile, Agile techniques
Improving the Team, Projects & Teams
Internet of Things/User Experience
Test & QA, DevOps, DevOps Implementation.

On the last day, the audience will have a tough choice as new tracks like Personal Excellence, Test Automation, Business Analysis & Requirements, Design & Code are added. Finally, the day ends with a Agile Leadership Summit Reception followed by Agile Leadership Summit.

We wish all the attendees a wonderful learning experience and we will be actively monitoring the Twitter world for the tweets and live blogs on the conference days.

Micro Sponsors
TestBash Philadelphia
Date: Nov 10–11, 2016
Location: FringeArts Theatre
Website: http://www.ministryoftesting.com/training-events/testbash-philadelphia-2016/

TestBash Philadelphia

TestBash Philadelphia

We always loved the energy of folks at MOT (Ministry of Testing). Their resources section is really a treasure mine for folks in software testing. You can also check out the page? – Resources. We have been following them and love the videos they record as part of TestBash or the 99sec talks. So, when we had a choice of sponsoring TestBash, we immediately grabbed it. We are sponsoring the TestBash Philadelphia. Check out the amazing speakers for this conference:

Fiona Charles: Gaining Consciousness
The last time I met Fiona was at CAST 2015 where I attended the tutorial on Speaking Truth to Power and how to deliver difficult messages. It was such an engaging tutorial where we learned to take baby steps towards being more courageous. Without any doubt, this session would also be a great one and engage testers. Do attend.

Alan Page: Testing without Testers
My first serious interaction with Alan’s work was with his book: https://leanpub.com/TheAWord Quite controversial and technical concepts presented in a simple, easy to understand manner. Even in his recent blog posts, his ideas of how to generate test data or test API is quite interesting. Do attend his talk to find out what he thinks about Testing without Testers.

Maaret Pyhäjärvi: A Mob Testing Experience
Reading the blog post on Mob Testing here: http://visible-quality.blogspot.in/2016/03/mob-testing-definition-and.html gives me some idea about Mob Testing. The participants must not miss the chance to hear her talk about it live.

Megan Studzenski & Cheri Kure: A Tester Training Program Awakens
Looking forward to the tweets about this session and best wishes to the speakers.

Nancy Kelln: What the Hell Kind of Testing is That?
I met Nancy in EuroSTAR 2010 first and then in Bangalore for a conference. Very experienced tester and she definitely knows how to get her point across in an engaging way. Her talk title made me smile and do not be surprised if some myths are busted in her session.

Abby Bangser and James Spargo: How we learned to stop worrying and start treating infrastructure like any other feature
This would be a new topic for me and I hope Twittersphere will help me with the insights from this talk.

Elizabeth Zagroba: Succeeding as an Introvert
After attending Problem Solving Leadership workshop, I could appreciate the different personality traits and how people respond to situations. Considering that we work with people more than products, this session should provide the attendees with lots of valuable takeaways.

Dan Ashby and Stephen Janaway: Testing In The Pub ­ Live!
If you would heard of the Testing in the Pub podcasts, this session must be an interesting one to know the history of Testing in the Pub. They are also planning to record one session live and demonstrate how anyone can easily contribute to the software community activities.

Angie Jones: How to Get Automation Included in Your Definition of Done
I have been following Angie on twitter and she seems quite active tweeting about the sessions she has been attending at different conferences and sharing the ideas.

Christina Ohanian: Embracing Change: The challenges of changing ‘traditional’ mindsets
Many of us face this challenge everyday. It will be a good experience to know what Christina has to share on this topic.

Israel Alvarez: Applying Newly Acquired Testing Skills on the Job
Learning is a continuous activity. What do you do after you learn something new related to software testing? Let us see how Israel Alvarez applied his skills on the job. Maybe, we can also learn how to implement our learning at our job.

Lanette Creamer: Test Like a Cat (Not a Dog)
If you are active on twitter, especially in software testing, you must already be knowing about Lanette. Experienced professional, cat-lover, a passionate advocate of whole team software quality, Lanette’s talk title is not surprising. With her rich experience of working in different contexts, this talk is a must attend for any software professional. Do not miss it.

Ash Coleman: Agile Tester Interactions: The Story Of Story Kickoff
She is already super famous in the software testing field as her first speaking experience was a debate against James Bach at Test Masters Academy. If we go by the Twittersphere, she was at her best – calm, composed and defended her points without any fear, backed up by insightful points. Do not miss her talk as she talks about the importance of story kickoff in an Agile setting.

We wish the attendees of both the conferences, a rich learning experience and total return for the time and money spent for the conferences. Make new friends, question the speakers and take back lots of thoughts and ideas to implement at your workplace.

Till we meet next time, happy testing!!!

 

Five Questions Series: Sahi’s Relational APIs

Posted by | features, web automation, xpath | One Comment

In the fourth post on the Five Questions Series, we have Sahi Relational APIs today.
Previous posts in this series: Sahi Controller, Sahi Logs and Sahi Excel Framework.

What is Sahi Relational API
Some times, elements are not uniquely identifiable by themselves. Identifying them in relation to either some element near them or by the element in which they are contained helps. Sahi Relational APIs help you solve that problem. The Relational APIs can be used even on applications with dynamic ids to easily locate one element with respect to another.

Please list the different APIs (markers) under DOM and Positional Relational APIs
There are 2 kinds of relation APIs: DOM Relation APIs and Positional Relation APIs. DOM relation markers like _near, _in specify that the element should be searched near or within another element. Position relations like under, rightOf, leftOf etc. relate one element to another via their position. The list is as follows:
DOM Relation APIs:
_near, _in, _startLookInside, _stopLookInside
Positional Relation APIs:
_rightOf, _leftOf, _leftOrRightOf, _under, _above, _aboveOrUnder
Parent APIs:
_parentNode, _parentCell, _parentRow, _parentTable

How to identify elements using relational APIs?
Identify the main element or the element which is easily identifiable. Then, anchor it and identify the (hard to identify) element in relation to the main element.
Let us take an example to highlight this. In the sample application, we have three books Core Java, Ruby for Rails and Python Cookbook. We also have a text field against each of them.

Relational APIs: Sample Application

Relational APIs: Sample Application

Suppose, we want to identify the text field against the Ruby for Rails. Notice the accessor of the element when no relational API is used. It reads _textbox(“q[1]”).

Relational APIs: Element Accessor without Relational API

Relational APIs: Element Accessor without Relational API

First, identify the main element. In this case, it is the label?-?Ruby for Rails.

Relational APIs: Identify Ruby for Rails

Relational APIs: Identify Ruby for Rails

Anchor the main element by clicking on the Anchor icon.

Relational APIs: Anchor the main element

Relational APIs: Anchor the main element

Identify the secondary element now. Observe the accessor field.

Relational APIs: Identify the second element in relation to the first element

Relational APIs: Identify the second element in relation to the first element

It reads: _textbox(“q”, _near(_cell(“Ruby for Rails”))).

What is the advantage of using _rightOf/_leftOf compared to _near
Using _near where the element to be found may or may not exist can give you unexpected results. For example, in the table below

Relational APIs: Sample Table with missing elements

Relational APIs: Sample Table with missing elements

Let us say we are looking to check if a delete link exists against all users.

_assertExists(_link(“delete”, _near(_cell(“User Two”)))) may be expected to fail, but it passes.
_link(“delete”, _near(_cell(“User Two”))) actually points to the above highlighted link.

This is because, _near is a DOM relation API and finds an element within 7 ancestors (parent nodes) of the given anchor. In our case this link was found within 2 ancestors of the cell in the next row.

The correct way of asserting this would be
_assertExists(_link(“delete”, _rightOf(_cell(“User Two”)))).
_rightOf forces location only along the same line.

Does Sahi Flex Library (SFL) support the Relational APIs?
Sahi Flex Library (SFL) supports near, inside, leftOf, rightOf and under APIs. The usage of these APIs is a little different from the Sahi relation APIs.
The relation APIs are called as member functions.
_f(“fid”).textinput(“u”).near(_f(“fid”).label(“User”))
_f(“mxC”).datagriditemrenderer(“/@fictitious.com/”).rightOf(_f(“mxComponents”).datagriditemrenderer(“Mary Jones”))

They can be chained to use multiple relations.
_f(“fid”).textinput(“u”).near(_f(“fid”).label(“User”)).inside(_f(“fid”).vgroup(“SettingsPanelView”))

Any other questions in your mind?
Feel free to comment or ask your question(s) and we will get back to you.

Sahi Pro: much more than an automation tool

Posted by | Uncategorized | No Comments

Everyone understands that software testing plays an important role in the overall quality of the product. When we test software, we would expect the teams to test on as many different quality criteria as possible, especially when we would like to expose the risks associated with different quality criteria. Gone are the days when something functional was accepted. Today, customers switch to your competitor the moment they see a dip in the quality of your product. This makes it imperative to have all the corners covered.

Functional Testing
Welcome Sahi Pro in to the picture. Many of you know Sahi Pro as The Tester’s Web Automation Tool. In this blog post, I want to highlight how Sahi Pro can help you cover multiple quality criteria with ease. Most of the testing cycles start with functional testing, smoke tests at the tester’s end. Sahi scores well in functional testing in terms of the following:
– Easy identification of elements
– Provides alternatives to element’s accessor
– Usage of Relational APIs (http://sahipro.com/docs/sahi-apis/relation-apis.html) which lets Sahi relate one element to another
One can use Sahi Pro to test each component individually without facing any problem w.r.t element identification.

Web Services
Sometimes, the UI is not ready for testers to test but the backend is ready and can be tested. If your application uses REST protocols, Sahi Pro comes to your help. Sahi exposes RESTRequest and RESTResponse APIs to work with REST APIs. So many times, everything seems to work fine at the UI layer and fails at the backend. This type of testing will help you understand and pinpoint the exact problem. Feel free to check out how you can use Sahi Pro to access Web Services through REST APIs here: http://sahipro.com/docs/faq/webservices.html

Data Driven Testing
You would also like to perform data driven testing on your application after your smoke tests no longer fail. You can also use Sahi Pro to test with a variety of test data. You could cheat sheets like Test Heuristics Cheat Sheet or You Are Not Done Yet to design your test data. More information on how to use Sahi Pro for data driven testing is here: http://sahipro.com/docs/using-sahi/excel-framework.html#Data driven testing

Even though you are confident of the application’s capability to handle any kind of data thrown at it, you would definitely worry on how the different browsers render your application content. With the constant battle among browsers to gain supremacy, you never know which browser and to be more specific, which browser version might be the nemesis for your support team.

Most Popular Browsers compiled by W3Schools

Most Popular Browsers compiled by W3Schools

Cross-browser Compatibility
So, it is a wise idea to test across browsers and browser versions. Imagine how much time it would take from your testing team’s schedule to test every browser and latest and two previous versions. Add Sahi Pro to your arsenal and Sahi Pro with its powerful multi browser and parallel playback features reduces your testing time for cross-browser compatibility by half. You need not even write any code for capturing screenshots on failure. Sahi automatically waits for page loads and captures screenshots on script failure.

Load Testing
You can now focus on load testing of the application. Sahi Pro lets you run load tests on your application. There are 2 Sahi scripts involved in this. One is used to generate the load. This script is called the noise and is run on a headless browser. The steps in the noise file are generally in an infinite loop so that they never terminate. The other script is called the subject. The subject is the script whose steps you would like to measure periodically at different loads. More details on how to configure and execute is here: http://sahipro.com/docs/using-sahi/load-testing.html

Localization Testing
Happy with the results so far, you now focus on your customers who are all around the world. You take a lot of pride in claiming that your application supports 10+ languages. As a tester, how confident that there are no missing strings or ui issues like overlapping, truncation or text bleed. Will you manually navigate to every screen and see if there are any English strings instead of the localized language? Fear not, use Sahi Pro, enable documentation checkbox to take screenshots at every step and use the power of _setLanguage API by Sahi Pro. Your localization testing is also taken care of. Details on the pre-requisites and configuration can be found here: http://sahipro.com/docs/sahi-apis/multi-language.html

Finally, you could also integrate with your build system and let Sahi Pro run the tests every time a build is triggered. You focus on the thinking part and let Sahi Pro take care of validating the builds and email you the status of the test suite. Your regression suite can be fully automated and you focus on the new changes, the discussion meetings and the cognition process.

If you have followed us so far, you now know that Sahi Pro can be used for
– Functional Testing
– Web Services Testing
– Data-Driven Testing
– Cross-browser compatibility
– Load Testing
– Localization Testing
– Regression Testing

Feel free to download a fully functional version of Sahi Pro from https://crm.sahipro.com/pay/index.php/registration/register and contact us at support[at]sahipro[dot]com if you have any questions.

Happy testing!!!

First Sahi Pro Meetup – How did it go?

Posted by | Uncategorized | No Comments

The first meetup of Sahi Pro was successfully organized.

Date: 26th Aug, 2016
Time: 3 pm to 6 pm IST
Venue: Tyto Software Pvt. Ltd., 1st Floor,
B.C.P. Towers, 386, 9th Main,
HSR Layout, Sector 7,
Bangalore 560102

We had three attendees and we started with a comprehensive demo of Sahi Pro’s features. After the demo, we answered the questions asked by the attendees with respect to their application. They were in the evaluation stage and were in need of an automation tool.
The attendees were pleased with the support they received in the meetup and we were happy that we conducted the first meetup of Sahi Pro to the satisfaction of the audience. Stay tuned for details about the second meetup of Sahi Pro.

Sahi Pro Meetup

Feel free to contact us at support@sahipro.com if you have any questions regarding Sahi Pro. Till next time, happy automating.

Team Sahi Pro’s solution at the Test Automation Contest

Posted by | Uncategorized | No Comments

After the blog post here, we asked Rahul Verma if we could publish our solution on this blog. We were concerned about the same problem given in future contests. After getting a go-ahead, we are here to publish and describe our solution. The application for this contest was “WordPress”. There were three scenarios to be automated within three hours. One of the main requirements was that these scenarios should run unattended.

Scenario 1: Publish five unique blog posts. Verify that the blog posts have been published successfully.
Scenario 2: Create a user and login with the created user.
Scenario 3: Search for a particular post and delete the blog post.

Our Approach:
We used Sahi Pro to automate these scenarios. We followed what we recommend to our users:
– Record with Accessor Repository enabled and create snippets of code
– Extract functions and use functions library
– Create Scenario files (.s.csv)
– Keep the data external to the script and call the file when required
– Club the scenario files into data driven suite (.dd.csv )
– Added tags for each scenario
– Execute .dd.csv from ant target

So, the final .dd.csv file is as follows:

blogTest.dd.csv

blogTest.dd.csv

Here, we are running three scenario files and tagged these scenarios with tags – all and scn1/scn2/scn3.
The scenario file for the first scenario is as follows:
We are logging in to the application and adding five unique blog posts. Once the posts are posted, we are verifying and finally logout of the application.

createBlogPosts.s.csv

createBlogPosts.s.csv

Let me describe the components of a scenario file here.
The first line of a scenario file is the column header – TestCase, Key Word, Argument 1, 2.
loadSahi loads the Sahi script with required function definitions. In this case, we are loading ‘blogARBlog.sah’ and ‘createBlogPost.sah’. blogARBlog.sah is the Accessor Repository file which we will know in detail later.
We are reading the data from an external file. In this case, it is a CSV file. So, we are using the _readCSVFile API
[Documentation] is useful for documentation purposes. One can note the purpose of the test case here.
In the [Data] [data:Posts:title] [data:Posts:content] [data:Posts:title], we are reading the data from the Posts.csv as per the column headings.
The other keywords are functions – login, addPostsAndVerify, logout.

As per our recommendation to our users, we also extracted functions and saved it in a separate functions library file.
The functions library file and the first script file is as follows:

functionsLib.sah

functionsLib.sah

createBlogPost.sah

createBlogPost.sah (Part 1)

createBlogPost.sah (Part 2)

createBlogPost.sah (Part 2)

We also used the Accessor Repository file in our scripts. This prevents the same element from being identified in multiple ways in different scripts. If there are changes expected in the element’s accessor, we need to update at only one place – the Accessor Repository (AR) file and all the scripts which include the AR file will be updated. This saves a lot of time and effort. The AR file for the first scenario is as follows:

blogARBlog.sah

blogARBlog.sah

And to identify the elements, we used our powerful recorder and object identifier which works on any modern browser. Once we ran the scenarios, the logs were automatically generated.

OverallLogs

OverallLogs

Scenario1Logs

Scenario1Logs

 

Finally, we generated the Ant Target and added to build.xml, configured Jenkins and ran the ant command from the command line.

Some of the unique features of our approach:

  • We did not use any waits throughout the whole exercise. Sahi Pro automatically waits for the whole page to load. It also waits for all the AJAX activities to complete. One need not add any explicit wait.
  • The use of relational APIs like _near which ensures that  the elements are identified in relation to an element we are sure of, which will not change its position.
  • We recorded on one browser and without any change in the script, we can play it back across browsers. We could also do a parallel playback using Sahi Pro.
  • Sahi Pro came up with the reports after playback without us writing any extra code.

You can download the code for the whole exercise here: stepin

If you also used Sahi Pro in the competition and followed a different approach, feel free to share your approach with us. Hope you liked our solution. Till next time, happy testing with Sahi Pro!

Sahi Pro powers Test Automation of eBaoTech’s Digital Insurance Platform

Posted by | Case study | No Comments
Sahi+eBaoTech

                                                                                                         Case study on eBaoTech

eBaoTech’s mission is to “make insurance easy”. With more than 150 installations in more than 30 countries, eBaoTech is one of the global leaders in insurance technology. From its inception in 2000, eBaoTech has been an innovation leader at the intersection of insurance and internet. eBaoTech offers world leading insurance software solutions for both life and general insurances.

Sahi Pro creates win-win situation for employee as well as employer where manual testers skill enhancement provides better job satisfaction to employee and employer gets the benefits of employee retention, automation and load testing.
– Rahul Agarwal, Manager Testing, Automation & QA
eBaoTech-Collaborus

Click here to download the complete case study.

Test_Automation_Contest

Team Sahi Pro – runner up in the Test Automation Contest at STeP-IN SUMMIT 2016

Posted by | Uncategorized | One Comment

Team Sahi Pro believes in continuous learning and we nominated ourselves for the Test Automation Contest conducted by STeP-IN Forum as part of STeP-IN SUMMIT 2016. Each team could have up to five members. We went with three members – our lead developer Kshitij Gupta, our support guru Pratik Shah and yours truly me (Ajay Balamurugadas). As soon as we got the email from the organizing committee about the pre-requisites, we kept asking them questions about the contest – the format, the purpose of VM, pre-requisites and what else was necessary from our side. Once we understood the expectations, we had all the pre-requisites in a pen drive and ready for the contest.

Contest Day:

We arrived on time for the contest and ready for the instructions. There was only one socket working in the power strip near our table. We quickly got it replaced and tested it. Then, once the pen drive was given to us with the VM image, we faced issues w.r.t network and BIOS settings. Virtualization was disabled in BIOS settings. Rahul explained the different types of networking modes like Host-only, Bridged and NAT. The volunteers from Test Mile helped us get ready for the contest. We received the problem statement at 9.35am. We quickly read the instructions and jumped to asking questions. It was soon announced that we will get time for asking questions.

There were three scenarios to be automated and the criteria to get selected for the final round was straightforward. The teams that had the scenarios automated would be through to the next round. There were a total of 32 teams participating and only 8 final slots. While Pratik started with the first scenario and Kshitij started working on the second scenario, I took the role of a business user who would keep cross checking the implementation against the requirement document. I took the role of timekeeper and noting down the team’s progress in a notepad.

Test Automation Contest

120 mins left for the contest to end:
We were clear on what to achieve at the end of the three hours and the progress was steady. None of the scenarios were automated till now. Work on the third scenario was not even started. At the same time, we thought that whatever we did till no was without any errors.

60 mins left for the contest to end:
Both the first scenarios were automated and the code was on two different machines. We also asked clarifying questions to the judges and were ready with some features that were over and above the expectations. While Kshitij refactored his code for scenario 2, Pratik ensured that his scenario 1 code worked without any errors. We wanted both the code snippets to be consistent with each other. So, we were also cross-checking the function names, password masking and the comments. Backup of each scenario was emailed to all of us.

30 mins left for the contest to end:
By now, we had integrated the code and started work on the third scenario. Some of the merge issues were resolved quickly. There were also some issues with Accessor Repository files. Each scenario was played back individually and the problematic line was identified. Though we were tempted to hard code the value due to lack of time, good sense prevailed and we troubleshooted it the right way.

15 mins left for the contest to end:
We started our work on Jenkins Integration and we tested our code on both the machines. One of them did not have Jenkins configured. As the clock struck 1pm, we were asked to close the laptops, wait for judges to judge us and head to lunch. We were satisfied with what we had achieved. Before we left, we had started the playback to verify one last time. The slides were also ready with our progress timeline, approach and the CTC (Challenges, Team work and Components) used. Then, judges came to us and asked to demonstrate our work. They checked if our code worked, which tool we used and the approach we followed. There were few questions asked and we confidently answered all of them to our satisfaction

After a good lunch, we were back to know who had qualified for the final round. We waited for more than 15 mins and we still did not know if we had qualified for the finals. Then the team names were announced. We were in the top 8. We were ready with the tweet and as soon as the name was announced, we pressed the ‘Tweet’ button.

Tweet

 

It was time for the presentations to begin. We were third in the presentation order. We connected our laptop and the HDMI cable to the projector. The input was not detected. We were given some time to sort it out. We tried installing drivers but it did not help. We had to try with the other laptop but remember, it did not have Jenkins. We quickly configured Jenkins on this machine and we were ready for our presentation.

Presentation Time:
We presented our approach, the code for each scenario, the challenges we faced and how we solved each challenge – the latest challenge being the HDMI connectivity issue. We also demonstrated our code by playing back the whole code. We highlighted the strengths of this approach and answered questions on why a particular approach was followed. There were questions on which parts we worked in the three hours and which came as part of the tool pre-packaged.

Team Presentation

Time for results:
Then the results for the Test Automation contest was announced along with highlights of each of the 8 presentations by the finalists. Team Sahi Pro came second and we were happy about it. One reason why we thought we missed the first prize was Sahi Pro is so feature rich that it might look that we did not do much in the 3 hours, which is acceptable. It is a testimony to the power of Sahi Pro. 🙂

Runner Up

Our special thanks to our CTO Mr. Narayan Raman for sponsoring this team for the contest. We also want to thank everyone at Sahi Pro for making Sahi Pro – The Tester’s Web Automation Tool. Looking forward to the next contest. Till then, happy testing with Sahi Pro!!!

Five Questions Series: Sahi Excel Framework

Posted by | Uncategorized | No Comments

In the third post on the Five Questions Series, we have Sahi Excel Framework today.
Previous posts in this series: Sahi Controller and Sahi Logs.

What is Sahi Excel Framework
The Sahi Excel Framework allows testers to write their test cases in Excel and run it from Sahi. Often a testing team consists of a mix of subject matter experts, some manual testers and testers with some automation experience. Writing tests in the language of the business allows all stake holders to participate and derive value out of the automation process.

Briefly, explain the syntax of Sahi Excel Framework.

Excel_Framework_001

Sahi Excel Framework

The first line of the sheet is the column header. All the blank lines are ignored.
loadSahi loads the Sahi script which has the functions defined in it.
Once you save the file, all the fields under the column Key Word become drop downs and you can choose your functions from the drop down.
[Documentation] row is ignored. You can use the Documentation row to highlight your test case summary.
Arguments are the parameters you pass to the functions.
// comments the step and does not execute the step.

As a domain/subject matter expert, how do I get started?
It is straightforward. Launch Script Editor and click on New > Scenario to launch a new file. Save it and start typing the function name in any of the rows under the Key Word column. You can then select the matching functions from the drop down. Once the functions are selected, enter the arguments for each function.

Now, include the functions library by pressing CTRL and clicking on any function. A Function Details popup will appear displaying the function details. You can view the function library or include it in the Excel file.

Function Details

Function Details

Modify the description for the test case, save the file and play it back.

What precautions will I have to take while creating the functions?
The functions you create will be used by the domain experts. So, make sure that the function names are easy to understand and descriptive at the same time. For example, verifyTotal is better compared to fn1550

How are the logs displayed?
When we run the Scenarios file, the logs clearly show the status of each test case followed by the time taken to run the test case. An overall status is also displayed along with total steps, time and browser details.

Scenarios Logs

Scenarios Logs


Any other questions in your mind?
Feel free to comment or ask your question(s) and we will get back to you.

Five Questions Series: Sahi Logs

Posted by | Uncategorized | No Comments

In the second post on the Five Questions Series, we have Sahi Logs today.
If you have not checked out our previous thread on Sahi Controller, click here.

How do you configure Sahi Logs?
There is no need to configure Sahi Logs separately. It is by default in-built within Sahi Pro. You need not write separate code to setup Sahi Logs. One can access Logs by clicking on Logs link from Sahi Dashboard or Sahi Script Editor. There is an option to view logs from Sahi Controller too.

Launch Logs

Launch Logs

What are the capabilities present in Sahi Logs?
For every script/suite played via Sahi, a log file is created. On clicking on Logs link, a window with the results in HTML is displayed. One can filter the results by using pagination tool or using SQL query.

Pagination_in_Logs

Pagination in Logs

SQL_in_Logs

The core capabilities include
– Logs for every script/suite
– Code Folding: When a function is called in a Sahi script, the logs for the function call are automatically “folded” in the reports
– Color coding of scripts, asserts and functions in red/green based on failure/success
– Script wise and Test Case wise summary
– Graphical representation of all scripts/suites run so far
– Comparison of suites where we can also compare screenshots, logs across scripts
– Detailed network activity for each request response

Code Folding

Code Folding

Graph

Graph


How can we monitor network activity in log files?
One can log HTTP request/response information for all network calls in the script. It is called HAR Logging. HAR refers to HTTP ARchive format of storing request response information. There are two ways to enable HAR Logging — globally or locally.

To enable HAR Logging Globally:
Add har_logging.enabled=true in userdata.properties and restart Sahi for this to take effect.

To enable HAR Logging Locally:
One can locally enable/disable HAR Logging inside a script using _startHarLogging() and _stopHarLogging() APIs.

An example of how HAR Logging would look is as follows:

HAR Logging

HAR Logging


Do logs record everything present in the script?
One has the option to mask certain information from appearing in the logs. Sometimes sensitive information like password, credit card details, bank account details may be entered via script, but we do not want it stored/displayed anywhere. We can then use APIs like _maskLogs to mask information and _unmaskLogs to start displaying steps in the playback logs and the Controller. This is mostly used after _maskLogs API.

Mask and Unmask Logs

Mask and Unmask Logs

How frequently are the logs updated?
Most of us want the logs to be up to date but do not like to refresh the logs page again and again. Auto Refresh Logs feature comes in handy here. By checking the ‘Auto Refresh Logs’ checkbox, the page is refreshed after every 2 seconds till the execution completes.

Auto Refresh

Auto Refresh

Any other questions in your mind?
Feel free to comment or ask your question(s) and we will get back to you.

Five Questions Series: Sahi Controller

Posted by | features, Sahi, tutorials | No Comments

Each week, we will pick a feature of Sahi Pro and hope to highlight its capabilities, benefits and tips on how to use it effectively by asking not more than five questions. We begin our Five Questions Series on Sahi Pro by focusing on Controller.

What is Sahi Controller?
Sahi Controller allows you to interact with Sahi and easily experiment and debug on the browser. Using Sahi Controller, one can easily identify elements, record and playback the scripts. One can launch Controller by pressing ALT and double clicking anywhere on the browser. Kick-start your web automation by recording using Sahi Controller and using the scripts as it is or creating functions out of the recorded snippets of code.

What are the capabilities of Sahi Controller?
Sahi Controller has many powerful capabilities spread across four tabs?—?Record, Playback, Clipboard and Info.

Sahi Controller

Sahi Controller

Record: This tab has controls to record a script. Recording is as easy as entering a name for the script and clicking on Record button. All the actions performed on the browser will be recorded and displayed in ‘Recorded steps’ tab.

One can identify elements using CTRL + mouseover and the Sahi Accessor for the element is displayed. Other actions like Click, Highlight, Set, Hover can also be performed on this element.

Action Buttons

Action Buttons

As seen in the image, each button invokes a        specific API.
  Click: _click API
  Hilight: _highlight API
  Set: _setValue API
  Hover: _mouseOver API

 

 

Assert: One can add assertions to verify if the end result is as expected. To add assertions, CTRL+mouseover an element. Click on ‘Assert’ button to view the possible assertions. It will be displayed in the ‘Evaluate Expression’ tab. Once tested, the assert statements can be appended to the main script.

Evaluate Expression: This can be used to evaluate snippets of Sahi code. Clicking on Test will evaluate the content and display the result (true/false/undefined) in the box below.

Smart dropdown for Evaluate Expression: If one wants to use Sahi API on only a part of the expression in the Evaluate Expression box, select the text and choose an action from the dropdown. This would in turn trigger an API and the results will be displayed in the box below. In this case, the ‘Is Visible’ option to trigger the API ‘_isVisible’ on the element ‘_textbox(“total”)’ is highlighted.

API on an element

API on an element

Playback: Using this tab, one can playback the scripts which are already recorded. Providing a Start URL and checking the checkbox will ensure that the script runs by first navigating to the URL mentioned. If the checkbox is not checked, the script will be executed on the current page without refreshing it.

Sahi Record Tab

Sahi Record Tab

Clicking on each of the links will open the respective window. For ex: Clicking on Logs will display the logs for all the scripts run so far. Clicking on a specific script on that page would display the specific logs.

Clipboard: This tab can be used to store small pieces of information.

Info: This tab shows the basic information of Sahi Controller, mode, browser, operating system and Java.

How are the elements on a web page identified?
Any element on the webpage can be identified by pressing CTRL and mouseover the element. The best Sahi accessor for the element is displayed by default in the Accessor field. One has the option to choose an alternative from the ‘Alternatives’ dropdown. Value shows the value of the current element. Prefix populates the prefix as needed when working with popup windows and multiple domains.

Element Identification

Element Identification

Tell us more about the Relational API and anchoring an element.
Sometimes, an element changes its position/name due to code changes and the whole script fails as the tool is not able to identify the element. To get rid of this issue, a very powerful option is Relational API and anchoring an element.

Let us take the following example where we have to identify the quantity field against “Ruby for Rails”.

Relational API

Relational API

If we identify the field in isolation, the Sahi Accessor reads:
_textbox(“q[1]”).
What if three more book titles are added before Ruby for Rails. The Accessor for the field against Ruby for Rails also changes. To avoid this situation, let us anchor the label ‘Ruby for Rails’ first and then identify the field against it.

Identify Ruby for Rails field

Identify Ruby for Rails field

Anchor the field

Anchor the field

Identify the quantity field

Identify the quantity field

How does recording with ‘Enable Accessor Repository’ on help?
If ‘Enable Accessor Repository’ checkbox is checked, Accessor Repository file text field appears. Once the user clicks on ‘Record’ button, Sahi will record using Accessor Repository. In the ‘Accessor Repository File’ text field, we mention the relative or absolute path to the Accessor Repository file.

Accessor Repository

Accessor Repository

Once a Accessor Repository file is chosen, an element will always be identified first by its AR entry, even when not in recording mode. This prevents the same element from being identified in multiple ways in different scripts.

When elements have been smartly identified using Relational APIs like _near or _under once, newer recordings on those pages will simply use the AR entry, so other users do not need to worry about doing it again or wrongfully using a different identification mechanism.

One important thing to note with Accessor Repository keys is that they must always be in the format $_ALL_IN_CAPS. If this is not followed, the scripts will still work fine, but the values will not come up properly in Script Editor’s context panel.

Any other questions in your mind?

Feel free to comment or ask your question(s) and we will get back to you.

Sahi Pro – Cheat Sheet for Download

Posted by | Sahi, tutorials | No Comments

When we start using powerful products like Sahi Pro, we look forward to using it to the fullest. Sahi Pro has many APIs that can help us with our testing. Some of the categories of APIs include
– File APIs
– Action APIs
– Fetch APIs
– Script Execution Control APIs
– Masking APIs

We have come up with a cheat sheet to help you refer to the different APIs at a glance. Download the cheat sheet from the below links:

cheat_sheet
PNG
PDF

Let us know what you think about the cheat sheet. Is it useful? Have we missed anything? Feel free to talk to us at support[at]sahipro[dot]com

MetricStream achieves quick ROI using Sahi Pro Web Test Automation Tool

Posted by | Case study, marketing, web automation | No Comments

MetricStream&SahiPro

MetricStream, a Leader in 2016 Gartner’s Magic Quadrant for Operational Risk Management Solutions and Forrester Wave on Governance, Risk, And Compliance (GRC) Platforms, is achieving quick ROI using Sahi Pro Web Test Automation Tool.

MetricStream’s GRC products are web-based applications built on technologies like Java, Ext JS, Ajax. They are using Sahi Pro to test their products in agile methodology and continuous integration. Sahi Pro Web Test Automation tool is being used for Frontend UI and Functional Validation.

MetricStream achieved several benefits by using Sahi Pro, and the most significant one was a reduction in overall regression test time and achieving an average savings of 70% to 80% on man hours of manual testing. Amongst other benefits, an important one was the ability of Sahi Pro to integrate with Jenkins and SVN to test builds in Continuous Integration.

Read More

Why Sahi Pro is much more than Record & Playback !!!

Posted by | Uncategorized | No Comments

Why Sahi Pro is much more than Record & Playback !!!

We associate few experiences to some phrases. The phrases immediately trigger back the memories to us. Some famous phrases in the realm of test automation include “100% testing”, “XPATH”, “record and playback”, “GUI Testing”, “Assertions”. One such phrase associated with strong reactions is “Record and Playback”. While some hate the limited capability of the record and playback mechanism and its brittleness in relation to the mouse coordinates, others like it for the simplicity and how it can be a quick and dirty solution.

Some perceptions take time to change. I was also of the opinion that Record and Playback tools meant unreliable and something that can be used only for a short period of time. My experience with AutoIt and the struggle with the mouse coordinates did not help change the perception. And then, I used Sahi Pro. The tagline is quite interesting—“The Tester’s Web Automation Tool”. I was curious as to why it was called the “Tester’s Web Automation Tool” and not just “Web Automation Tool”. I got my answer as soon as I started to play with the tool. It starts as a record and playback tool and extends itself much beyond that.

Power of Java within Sahi

For a start, one can use Java libraries right from the Sahi Script. Sahi’s JavaScript is executed in a Rhino JavaScript Interpreter, running inside Sahi’s proxy. As Sahi scripts run on the Rhino JavaScript engine, this allows Sahi to call any Java code in the classpath of Sahi. What does this mean to someone who is experienced in programming languages? They can use Sahi Pro to write powerful scripts quickly by making use of the many Java libraries available. They can test Java classes by writing scripts.

Powerful Accessor Repository

When you record, you can have Sahi Pro create a Accessor Repository(AR) file for you by turning on the ‘Record with Accessor Repository’ option. Once a Accessor Repository file is chosen, an element will always be identified first by its AR entry, even when not in recording mode. This prevents the same element from being identified in multiple ways in different scripts. One can thereby get rid of the brittleness of the recorded scripts. There is also provision to modify existing AR entries.

Use ( . ) to get attributes

Adding a dot (.) after the accessor in the accessor field, shows all the properties of the accessor. Further typing narrows down the list of properties.

Accessor

Clicking on an option (say, disabled) or typing .disabled directly in the accessor field and pressing Enter will populate the value in the “Value:” box. (In this case, .disabled is false)

Clicking on Assert will create an assertion for just that property.

Excellent logs and reporting mechanism

When record and playback tools restrict themselves to the recording of the scripts and the tester has to write code to get logs and reports, Sahi Pro is different. One does not have to write a single line of code to get the logs, reports of the scripts/suites. It’s inbuilt logging and recording feature is quite handy. One could also run SQL on the reports to get the exact report they desire.
Logs

Distributed Playback

I don’t think many record and playback tools, in fact many automation tools provide the feature of distributed playback. What Sahi Pro does is something quite amazing. You can play multiple scripts at once – on a single machine or even better across machines. Do you know any other tool which can run multiple instances of Internet Explorer on the same machine? Sahi Pro does it with ease.

Distributed Playback

With such powerful features, Sahi Pro not just relies on record and playback but is much more powerful. So, as a tester you can start with Record and Playback and build on it based on the context. Start adding assertions, create functions at the click of a button, use the common accessor repository or use the exhaustive documentation about the different APIs supported by Sahi Pro.

It is time to change your perception about record and playback tools and consider Sahi Pro to be the Tester’s Web Automation tool. Try it out here and let us know what you think. Here is the quick tutorial to get you up to speed.

Interview with Sahi Pro – The Tester’s Web Automation Tool

Posted by | Sahi, web automation | No Comments

I am Ajay Balamurugadas and I welcome you to our weekly show where we interview one of the promising leaders of the industry. It gives me immense pleasure to introduce today’s guest. He has been a consistent performer in web automation and built a strong hold in a very competitive market. When everyone built the automation frameworks, he focused on what is important – automating the checks. His unique philosophy of helping the tester makes his tagline – “The Tester’s Web Automation Tool” the Sahi (correct) tagline for him.

Without further ado, let us welcome –
Sahi Pro: The Tester’s Web Automation Tool

Ajay(A): Hello, Sahi Pro. Welcome to the show. We are very excited that you are here today to interact with us and share your expertise. You are one of the few automation tools who is tester-friendly and gets the job done in a simple manner. Tell us about yourself and your journey.
Sahi Pro(SP): Thank you, Ajay. It is my pleasure. I started as an open source product and then due to customer commitments, I started to focus on my Pro version and fulfill customer expectations. I noticed excellent testers struggling to automate due to complex automation tools. So, I evolved to enable subject matter experts and testers to get into automation easily.

A: Yes, that is indeed strange. When everyone around you focuses on building a robust framework and turning testers to coders, you have taken a different route altogether…
S: I will not say that we have a taken a different route for the sake of being different. My thought process is continuously evolving based on the testing industry and trends. I quickly realized that most of the end users were expected to be technical programmers or automation engineers. They were expected to build a framework from scratch, get the developers write code to align with the element identification mechanism and after all this, focus on automating the checks.

I found it quite disturbing. The purpose of web automation is to automate the checks, give the testing team the confidence that the regression bugs they expected to find are not present. The tool should free up the tester’s time. Testers should explore the application and find more critical bugs. I don’t expect my users to be technically super-strong. I take care of everything to help the tester, right from identifying the elements, suggesting accessor alternatives, providing relational APIs, excellent logging and reporting, calling Java functions and libraries from my script, automatic screenshots on failure and believe it or not, I automatically wait for page loads and AJAX activities to end!!!

A: Whoa! That’s quite a big list of key differentiators! Tell us about your element identification mechanism.
S: I use my own wrappers around the Javascript DOM to identify elements. My APIs use various DOM attributes of an element to identify them. Instead of relying on a single attribute, I look for the element’s value, name, id, css class or index etc. So, I work well even if multiple elements have the same attribute value. If I am unsure about a particular element’s identification, I rely on my trusted advisor – the Relational APIs to identify one element with respect to another.

A: Many testers want to learn automation and give up as soon as they face problems in learning a particular language. What is you suggestion to them?
S: Yes, that is a common story. People are spending time learning the language more than automating the tests. I am not against anyone learning a language but let us remember why we started this discussion. A tool should enable people to automate and not set restrictions on the way. I am an extension of JavaScript and have a pretty good recorder which can create scripts for further usage. If you have never used any tool for automation, try me!!! If you already burnt your hands spending a lot of time learning a language with little success, let us pair together and see if I can help achieve your goals.

A: Are you only for newbies or can experienced folks take advantage of your prowess?
S: As I have already highlighted, my recorded scripts can be used as a good starting point for further scripting. My JavaScript is executed in a Rhino JavaScript Interpreter, running inside my proxy. As Rhino is a JavaScript runtime running inside a Java Virtual Machine (JVM), this adds a lot of power to my scripts. My scripts can directly call Java code in scripts.

A: I am sure, our readers are excited to try you and your APIs. Does anyone provide training or demo about you?
S: The folks at Tyto Software Pvt. Ltd seem to be quite helpful in this regard. Shoot an email to info[at]sahipro[dot]com or check out the documentation about me at http://sahipro.com/docs/introduction/index.html
I also meet my friends every Thursday in a webinar at www.sahipro.com/webinar

A: Thank you for your time, Sahi Pro. We wish you all the best for your future releases and features.
S: My pleasure. All the best for your series too.

Feel free to add your questions as comments and we will get Sahi Pro to answer for you.

Five salient features of Sahi Pro that may surprise you!!!

Posted by | features, Sahi, web automation | No Comments

I have been using Sahi Pro for some time and each time I face an issue, the Sahi Documentation has been of great help to me. Apart from the documentation, one would also appreciate the number of example scripts bundled with the product. After testing Sahi Pro on a variety of applications, I could not hold myself from highlighting  few salient features of Sahi Pro that may surprise you.

Automatically waits for AJAX and page loads

The first tool I used to automate my tasks was AutoIt and I had to add lots of Sleep(5000) or WinWaitActive ( “Create a New Post”, “” , 10 ). A quarter of my code had these Sleep commands. I had realized that these commands were very powerful essential to ensure that my scripts did not fail during the demo. Then I shifted to Selenium and things were no different. My friends who used Selenium in their day to day work had explicit code for wait.

And when I started using Sahi Pro, I was surprised at how Sahi Pro automatically waits for all the AJAX activities to finish and waits till the page loads completely. I did not have to add even a single line for wait. Isn’t it surprising? What surprised me more was that it was NOT necessary to have the browser in focus.

Record in one language and playback in another language

Do you know the average number of languages the top 25 websites support? As per the Web Globalization Report Card 2015, the number is 45. Very soon, you will have your web application support multiple languages. It is quite easy to automate for English language but your customers are from different countries and use other languages.
What would be the cost of automating across languages? Think in terms of the language experts, the automation engineer effort and the confidence you get with such an exercise. Just when we thought that it would be a costly exercise, Sahi Pro comes to the rescue with the API named _setLanguage
More details about the API here.

In-built reporting system and automatic screenshots on failures/errors

It is no wonder that people love reports. Even if someone is not willing to get technical about what’s happening in the code, they want the high level reports. How the product is performing over a period of time? How are we on the automation front? When was the last time the automation suite passed without any failures?
Creating an automation suite is itself a challenging task and to build a custom reporting module is no mean feat. Sahi Pro’s reporting module is amazing and will surprise you with the clarity of reports.And every time the script fails, Sahi Pro will automatically capture a screenshot. One need not add explicit code to take screenshots.

Excel framework – Faster collaboration between domain experts and automation engineers

Sometimes, it is easier to automate scenarios than to convince people of the value of automation, done right. People resist change and fear if their jobs will be replaced by automation. Domain experts are not willing to accept that they are not strong in programming skills and automation engineers are not sure if they are automating the right stuff.

Imagine a platform for the domain expert to provide their views and the automation engineers use the input to translate it to code. Sahi Pro’s Excel Framework aims to be the platform. The domain experts need not know how the code is implemented. The intent and the implementation is clearly separated in the framework.

Call Java libraries and APIs from Sahi Script

Sahi’s Javascript is executed in a Rhino Javascript Interpreter, running inside Sahi’s proxy. Only relevant individual statements are sent to the browser for execution. The rest of the runtime happens in Rhino inside Sahi’s proxy.
Rhino is a Javascript runtime running inside a Java Virtual Machine (JVM). This adds a lot of power to Sahi scripts. Sahi scripts can directly call Java code in scripts.

Isn’t it wonderful that you can leverage the power of Java libraries and APIs directly from your Sahi Script? Add to it, the power of Relational APIs like _near, _rightOf, _under and you will be surprised at how easy it is to use Sahi.

Have you used Sahi Pro? Which features are your favorite? I have listed my favorite five. Let me know your favorite ones in the comments.

If you are new to Sahi Pro, check out the weekly webinar at www.sahipro.com/webinar

Five reasons why Sahi Pro is not for you

Posted by | Sahi | No Comments

Sahi Pro is NOT the Sahi Choice, Baby !!!

Everywhere you see, people sell you something or the other. Someone asks you to buy food from their app, someone asks you to book flight tickets while someone else is ready to help you find the right job for you. We are surrounded by products and services. Consider the field of web automation and there are at least ten products you can name right now. Are they worth the hype? That’s a different story for another day. Today, I want to highlight why Sahi Pro is not the right choice for you.  Yes, you read it right! Why Sahi Pro is not the right choice for you!!! I will give you five reasons and you can let me know which one is true in your case.

Reason 1: Already Budgeted and Approved.

You planned for the automation in your testing strategy. You finally got the plan approved by your manager. The budget for the automation team was approved. Your whole plan is ready and you love playing with XPaths.  After so many days, if you go for Sahi Pro now, all your plans will go haywire. You don’t want to risk that danger. You don’t have the courage to accept the change in plan to your manager. If this is the case, I promise you Sahi Pro is not the right choice for you. As Sahi Pro doesn’t rely on XPaths, it will expose your poor planning. So, don’t go with Sahi Pro and continue playing with XPaths and the game of thrones identifying elements.

Reason 2: Automation Engineers will lose their jobs.

You are proud of your strong team of automation engineers. You did not make the mistake of hiring a tester and turning them into bad programmers. You hired quality automation engineers and that masterstroke is still praised by many. Any requirement for automation and your engineers love it. They jump on it and finish it to everyone’s satisfaction. Everyone knows that you don’t really need specific automation experience to get started with Sahi Pro. The moment you get your hands on Sahi Pro, you will have to bid goodbye to your team members. You will be asked questions like “Why did we not use Sahi Pro till now?”, “If we don’t need automation engineers from today, why did we have them till yesterday”. Many more such tough questions would be fired to you and you will have to deal with them. The easiest way to avoid such questions is to continue the existing plan, team and forget about Sahi Pro.

Reason 3: Testers favorite and no more regression testing.

Many test leads are afraid of regression bugs (bugs found during regression testing). They delay the new feature development and focus on regression testing for many days/weeks to avoid such bugs. As of today, you ask your testers to focus on ensuring that nothing breaks due to new code/fixes. The day you get Sahi Pro, testers will love it and focus on Sahi Pro to automate the regression scenarios. Their focus will now shift to finding new bugs and take up the investigative role rather than confirming that old things continue to work.

Isn’t that a big risk you will take? More bugs would mean delayed releases and what will happen to your reputation then? Who will protect it? Better ignore Sahi Pro and let the new bugs lay hidden in the code.

Reason 4: You are too organised to like Sahi Pro.

Like every other company, you proudly advertise that your product works on almost any web browser. As you are too organised in your professional life, you love to maintain scripts for each browser separately in a separate folder. You don’t believe in the concept of one script that runs on multiple browsers. It looks like a big joke to you. Alas, Sahi Pro has the feature of One Script – Run on Multiple Browsers and hence, it fails to impress you.

Accept our sincere apologies and continue to write individual scripts to suit each browser. The last time we contacted Sahi Pro, they were not ready to remove that feature.

Reason 5: You refuse to acknowledge ‘Sunk Cost Fallacy’.

You spent money hiring a team, building an automation framework, buying an expensive tool and trying to change everything under your control to make the automation a huge success. A small change in the application is making your team put in extra hours. Everyone is able to see that it is more costly to maintain the automation scripts compared to the value by running them. Yet, you have taken it to your heart and refuse to acknowledge the ‘Sunk Cost Fallacy’.

Like many of us, you repeat this to yourself multiple times:
“We have invested so much money in it. If we stop now it will all have been for nothing.”
You are right. There is nothing called Sunk Cost. You carry on with the existing tool till you leave the job. Sahi Pro will ensure that you get out of the fallacy, which is dangerous.

Many folks have one or the other reasons not to use Sahi Pro. What about you? 

Sahi Pro helps

  • identify elements easily
  • by making life of automation engineers and testers better
  • testers to find new bugs
  • by making a single script run on multiple browsers
  • you get out of the trap and actually save money and time.

    We are just an email away: info[at]sahipro.com

Feel free to approach us. We love solving authentic problems. There is a weekly webinar that talks about Sahi Pro every Thursday 8.30pm to 9.30pm IST. Do attend and pass this information to anyone who would be interested.

Sahi_Webinar

Use fully-loaded Sahi Pro FREE for a month. Download Now Request a Demo