Skip to main content

E-Commerce and Testing

History of E-Commerce

Doing trading something over the internet is simply called as electronic commerce, shortly e-commerce or eCommerce. The technology of e-commerce goes back to the 1979 when Micheal Aldrich introduced first online shopping system. Then Tim Berners-Lee used NeXT computer to create first web browsers and called it World Wide Web (www). When we came to 1995, the first e-commerce website amazon.com was launched by Jeff Bezos and later on the same year, ebay.com was launched by Pierre Omidyar. If we look at what happened this year, according to the b2b2dot0 which has gained this information from SAP-integrated eCommerce solution, for the 2nd quarter of 2013 the revenue is 147 Million dollars and 326 Million for 1st and 2nd quarters in total for only B2B market. According to the Forrester study prediction about 2013, 559 Million dollars for B2B market and 252 Million dollars for B2C market will be released.


Second Quarter of 2013 E-commerce Values

 

Type of E-Commerce

There are many types of selling or buying activities over internet. Commonly people understand from the e-commerce as customer uses a website of a seller and buying something. This kind of e-commerce is related to customer and seller, or business, so it is called as business-to-consumer e-commerce model or shortly B2C. There are many examples for this kind of e-commerce, such as www.amazon.com, www.bestbuy.com, hwww.shopbop.com. If the business sells product to business, generally big wholesaler sells the product another dealer, this kind of e-commerce is called as business-to-business or B2B. This kind of e-commerce is used for supply chain management. For example www.alibaba.com, www.busytrade.com, www.made-in-china.com are very famious B2B e-commerce sites. According to the A.Koponen, B2B market is growing faster than B2B market and %80 of the e-commerce is B2B. Consumers also sell his products or goods directly to another consumer, this kind of e-commerce is called as consumer-to-consumer, or C2C. Generally auction website like www.ebay.com, www.ltainenporssi.fi, www.sahibinden.com are this kind of e-commerce.  In developed countries doing governmental issues, like taxes procedures can followed by internet, or accessing government database for someone’s credibility status online by a private bank, are a kind of e-commerce and called as business-to-government e-commerce, or B2G. By use of mobile devices, generally smart phones,  are getting widen, there has been demand on using mobile devices for daily needs such checking weather, following favourite news, buying or selling units in stock market, playing games, and lots of others. This kind of e-commerce is called as mobile commerce, or shortly m-commerce.  This kind of applications can be loaded from the market provided by vendor of the operating system like android by Google, ios store by Apple, appworld by BlackBerry, appstore by Windows. Some studies shows that the next-big thing will be m-commerce, according to the prnewswire, in 2013, there will be 251 Billion mobile transaction and there will be competition to take part of m-commercing by the firms.

What About Testing E-commerce Sites

Since there has been increasing demand of trading online, the number of any kind of e-commerce application is in trend of increase. Therefore the competency among the e-commerce firms is very hot and this shape their vision to release new features to the market and quality policy. Releasing quality product is important but releasing quality product to market on time is very important so time-to-market is another important attribute for competition. 

The next post will be related to testing e-commerce application effectively and efficiently.


 

Popular posts for software testing and automation

Selenium Error "Element is not currently interactable and may not be manipulated"

Selenium webdriver can drive different browsers like as Firefox, Chrome or Internet Explorer. These browsers actually cover the majority of internet users, so testing these browsers possibly covers the 90% of the internet users. However, there is no guaranty that the same automation scripts can work without a failure on these three browsers. For this reason, automation code should be error-prone for the browsers you want to cover. The following error is caught when the test script run for Chrome and Internet Explorer, but surprisingly there is no error for the Firefox. Selenium gives an error like below: Traceback (most recent call last):   File "D:\workspace\sample_project\sample_run.py", line 10, in <module>     m.login()   File "D:\workspace\ sample_project \test_case_imps.py", line 335, in login     driver.find_element_by_id("id_username").clear()   File "C:\Python27\lib\site-packages\selenium-2.35.0-py2.7.egg\selenium\webdriver\r

Change Default Timeout and Wait Time of Capybara

One of the biggest challenge for automation is handling timeout problem. Most of the time, timeout is 60 seconds but it may sometimes not enough if you have badly designed asynchronous calls or the third party ajax calls. This makes handling timeout more complex. set large enough to tolerate network related problems. For Selenium based automation frameworks, like Capybara, default Webdriver timeout is set to Net::ReadTimeout (Net::ReadTimeout) Changing ReadTimeout If you have timeout problem for Capybara, it gives an error like above. This means that the page is not fully loaded in given timeout period. Even you can see that page is loaded correctly but webdriver wait until the Ajax calls finish. class BufferedIO #:nodoc: internal use only def initialize (io) @io = io @read_timeout = 60 @continue_timeout = nil @debug_output = nil @rbuf = '' end . . . . . def rbuf_fill beg

Page-Object Pattern for Selenium Test Automation with Python

Page-object model is a pattern that you can apply it to develop efficient automation framework. With the page-model, it is possible to minimize maintenance cost. Basically page-object means that your every page is inherited from a base class which includes basic functionalities for every page. If you have some new functionalities that every page should have, you can simple add it to the base class. Base class is like the following: In this part we are creating pages which are inherited from base page. Every page has its own functionalities written as python functions. Some functions return to a new page, it means that these functions leave the current page and produce a new page. You should write as much as functions you need in the assertion part because this is the only part you can use the webdriver functions to interact with web pages . This part can be evaluate as providing data to assertion part.   The last part is related to asserting your test cases against to the

Create an Alias for Interactive Console Work: Selenium and Capybara

If you are working on shell most of the time Aliases are very helpfull and time saving. For testing purposes you can use Alias for getting ready your test suites. In this post, I want to explain both running Selenium and Capybara on console and creating aliases for each.  This post is for Windows machines, if you are using Unix-like see   this post . Creating Scripts for Selenium and Capybara First of all, it is assumed that you have installed Selenium and Capybara correctly and they work on your machines. If you haven't installed, you can see my previous posts. I am using the Selenium with Python and the Capybara with Ruby. You can use several different language for Selenium but Capybara works only with Ruby.  Create scripts in a directory called scripts (in your home folder, like as  ~/scripts ) for your automation tool as following, save them as capybara.rb, sel.py :  Creating Aliases Depends on your favourite shell, you need to add the alias to .bashrc bash

Performance Testing on CI: Locust is running on Jenkins

For a successful Continuous Integration pipeline, there should be jobs for testing the performance of the application. It is necessary if the application is still performing well. Generally performance testing is thought as kinds of activities performed one step before going to live. In general approach it is true but don't forget to test your application's performance as soon as there is an testable software, such as an api end point, functions, and etc. For CI it is a good approach to testing performance after functional testing and just before the deployment of next stage. In this post, I want to share some info about Jenkins and Locust. In my previous post you can find some information about Locust and Jenkins. Jenkins operates the CI environment and Locust is a tool for performance testing. To run the Locust on Jenkins you need command line arguments which control the number of clients ,   hatch rate,  running locust without web interface and there should be so