Trade Me - Senior Software Test Analyst: Difference between revisions

Jump to navigation Jump to search
m
Line 58: Line 58:
* Chrome extensions ([https://chromewebstore.google.com/detail/custom-javascript-for-web/ddbjnfjiigjmcpcpkmhogomapikjbjdk?pli=1 '''CJS Custom JavaScript'''], [https://chromewebstore.google.com/detail/bug-magnet/efhedldbjahpgjcneebmbolkalbhckfi '''Bug Magnet'''], [https://chromewebstore.google.com/detail/clear-session/maejjihldgmkjlfmgpgoebepjchengka '''Clear Session'''], Responsive Web Ruler,  WASP etc).  
* Chrome extensions ([https://chromewebstore.google.com/detail/custom-javascript-for-web/ddbjnfjiigjmcpcpkmhogomapikjbjdk?pli=1 '''CJS Custom JavaScript'''], [https://chromewebstore.google.com/detail/bug-magnet/efhedldbjahpgjcneebmbolkalbhckfi '''Bug Magnet'''], [https://chromewebstore.google.com/detail/clear-session/maejjihldgmkjlfmgpgoebepjchengka '''Clear Session'''], Responsive Web Ruler,  WASP etc).  
* Developer tools on tier 1 browsers
* Developer tools on tier 1 browsers
==API First Policy==
: Trade Me started in 1999 when API's weren't part of the IT landscape, and their flagship desktop browser website application did not implement an API. However, since then we have seen the rise of mobile devices and with it the desire to use API's to implement business logic separate from a proliferation of user interfaces and technologies. Trade Me now has a number of mobile apps for Android and iOS devices, and several business to business interactions all connected via their API. The desktop website has always been the most fully featured of their applications and most new features were developed first (or only) for the desktop website. This was becoming a serious drag on implementing the mobile solutions and the company adopted the policy ''API First''. It meant that any new feature destined for the desktop website would first need to implement the feature in the Trade Me API so that it could also be implemented in the mobile solutions when needed.
:This meant that all product squads were required to develop and deliver API solutions and API testing was part and parcel of my routine work. The API testing work was divided between tool assisted exploratory testing using an in-house developed API test tool. In addition we also implemented API automation cases using SoapUI (part of Ready!API), which were then merged into the general API Automation code repository.


==Projects==
==Projects==

Navigation menu