cancel
Showing results for 
Search instead for 
Did you mean: 

Day 1 - API Testing vs. UI Testing

Highlighted
Community Manager

Day 1 - API Testing vs. UI Testing

Hello API Community,

 

I’m happy to welcome you to our API Testing vs. UI Testing competition. We aren’t going to fight. We are going to identify what it is like - “Doing API Testing”.

Each day, we will publish a new topic to discuss. Leave your comments in topics - you and your API Team will be rewarded.

 

Today, let’s introduce ourselves to the Community! Post a high-level description of the project you are working on.

 

Leave your comments here.

 

API Testing Score

Track the current score and daily conversations on this page:

https://community.smartbear.com/t5/custom/page/page-id/API-Testing-vs-UI-Testing

 

Bonus Tasks

Accomplish any of the bonus tasks to earn more points:

  1. +2 points - Invite your colleague to the competition.

Mention a nickname of this person by using @ in the competition’s daily topics. You can invite as many people as you wish. NOTE: A person you invite should be a new Community member registered after the event start.

 

  1. +2 points – Make a post on social media about your participation in the competition.

Your post should contain: @smartBear, the #APIvsUITesting hashtag and the link to your comment in the Community.

Simple tweet: API Testing vs UI testing! Which one is more important? Join me in the @smartBear Community to talk about this: https://bit.ly/2HEZ5U4 #APIvsUITesting

 

Event Rules

  1. Leave your comments on a conversation of the day. 1 comment = 1 point to the team score.
  2. The competition will be held on March 25-29.
  3. Join the competition any day and participate in any daily conversations.
  4. Feel free to leave comments for any teams.
  5. Rewards! A team with the biggest score will win. Active participants from each team will be rewarded.

 

Let's start!

---------
Tanya Gorbunova
SmartBear Community Manager

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others.↓↓↓↓↓
Tags (1)
11 REPLIES 11
Community Leader

Re: Day 1 - API Testing vs. UI Testing

Hi Community,

 

Currently, I am working for a retail and ecommerce based client. Their requirement is to replace all the massive mainframe with cloud microservices and to keep the individual services small, with responsibilities distributed accross a number of services. Coming to microservices testing part, I have to build a kind of framework using Rest-Assured/ReadyAPI to automate all the microservices.

 

Choice is mine....!!!

 

Thanks,

avidCoder.

Member

Re: Day 1 - API Testing vs. UI Testing

Currently Im working on Project Management application for smoke test scripts .

The main challenge that I have created a script  and If I run a test and it passes one day but not the next day because the object names are clearly not the same (ie.,Object id’s are changing) I'll do an object spy and fix. Might work for that day and then another test run, objects will fail

 

We haven't found the solution yet  ,  it would great if any solve our problem.

Community Hero

Re: Day 1 - API Testing vs. UI Testing

Happy to be part of this event,

 

We are automating Rest API calls for Telecom and Networking domain which is integrated with JSwing Application and Angular JS application.


Thanks
Shankar R

LinkedIn | CG-VAK Software | Bitbucket | shankarr.75@gmail.com

“You must expect great things from you, before you can do them”


Extension Available

Contributor

Re: Day 1 - API Testing vs. UI Testing

Hi Team,

 

I am currently working on test automation within the public sector to bring citizens and government closer together and facilitate communication between them.

API testing was a must and ReadyAPI quickly prooved to be the most promising tool (and it delivered! Smiley Happy). For UI automatision I also reviewed TestComplete, but at that time (2 years ago) we decided not to go with this tool. Reasons: I couldn't get it up and running that easily (I rememeber recording an easy script and couldn't get it to run it again), but most importantly because there was/is some in-house knowledge on the (free) Selenium framework. So we still use this framework for UI testing to complement the API testing.

However; choice for me personally is API testing, seeing it enables a shift to left in testing and helps to deliver quality even before a front end comes into play. UI automation for me now is mostly pure front (cross-)browser related tests, like logging in/out, check hyperlinks, sorting, filtering, etc.) and serves more as a regression test, while the API testing really covers the most part of the functionality (positive, negative testing, performance, security, authorization, authentication, flowtesting, destructuve, concurrenty, ...) + trying to cover new features each sprint.

 

...so GO API team Smiley Wink

Occasional Contributor

Re: Day 1 - API Testing vs. UI Testing

Happy to be part of this event,

 

We are automating Rest API calls for angular nodejs Application

Contributor

Re: Day 1 - API Testing vs. UI Testing

Currently working on UI testing but moving towards API testing. Facing lot of challenges with integration between a desktop application and service calls

Community Hero

Re: Day 1 - API Testing vs. UI Testing

Using SoapUI till recently for SOAP and REST API testing and execution with Apache-Ant for execution of the tests and report creation.

 

If some one has project, and like to execute it and generate reports, then simply use docker image



Regards,
Rao.
Community Hero

Re: Day 1 - API Testing vs. UI Testing

This comment is generic which includes both UI and API test automation.

 

I know many start some kind of automation for web apps i.e., UI Automation. There are many open source and paid softwares available for the same using various technologies and programming in different languages

And many tools also allows record and play which may fit for some projects and many not be for some projects. And many expertise available in the domain as well thru various forums.

 

However, when it comes to API testing, and more evolving towards Microservices, this area is picking a lot know in the market.

But, for QA / Test engineers it is a bit challenge to test and automate the entire business flows as there is no UI for those who coming from web app testing. It requires data to be used from one API call response to the following request, data comparision as part of verification etc.

Either it needs complete programming skills( unlike web, no record and play possible here) to create some kind of framework.

Other demand is to be able to adjust for the Ajile model, do quick releases to reach market demand. 

Of course, there are tools available in this area too, but tricky to use.

Luckily, SmartBear has both free and paid products  which not only allows to test customer products, but also enabling the teams to automate their business functionality.



Regards,
Rao.
Regular Contributor

Re: Day 1 - API Testing vs. UI Testing

Hi Community Members,

 

I have done UI Testing and API Testing in my small career using UFT, but since past 2 years i am doing API Testing using ReadyAPI, i am currently working on banking domain and automating REST based services.

 

 


Click "Accept as Solution" if my answer has helped, and remember to give "kudos" Smiley Happy

Thanks and Regards,
Himanshu Tayal
New Here?
Join us and watch the welcome video:
Top Kudoed Authors