Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
PhantomJS Cookbook
PhantomJS Cookbook

PhantomJS Cookbook: Over 70 recipes to help boost the productivity of your applications using real-world testing with PhantomJS

eBook
€18.99 €27.99
Paperback
€34.99
Subscription
Free Trial
Renews at €18.99p/m

What do you get with Print?

Product feature icon Instant access to your digital eBook copy whilst your Print order is Shipped
Product feature icon Paperback book shipped to your preferred address
Product feature icon Download this book in EPUB and PDF formats
Product feature icon Access this title in our online reader with advanced features
Product feature icon DRM FREE - Read whenever, wherever and however you want
Table of content icon View table of contents Preview book icon Preview Book

PhantomJS Cookbook

Chapter 2. PhantomJS Core Modules

In this chapter, we will cover:

  • Inspecting the version at runtime
  • Managing cookies with the phantom object
  • Specifying a path for external scripts
  • Setting up a global PhantomJS error handler
  • Controlling the exit status of a PhantomJS script
  • Inspecting command-line arguments
  • Inspecting system environment variables
  • Saving a file from a PhantomJS script
  • Reading a file from PhantomJS
  • Creating a custom module for PhantomJS
  • Loading custom modules in PhantomJS

Introduction

PhantomJS exposes several core APIs to work with the headless browser and with the operating system that hosts the runtime. For example, we can get information about PhantomJS, inspect our host environment for values assigned to variables, and read from or write to the filesystem with the help of these APIs.

The recipes in this chapter will focus on those APIs that are considered part of the PhantomJS core. Specifically, we will introduce and discuss the global phantom object, the system and fs modules, and how to create and load our own CommonJS-compatible modules.

Inspecting the version at runtime

This recipe will introduce the global phantom object in PhantomJS and discuss how we can inspect the version at runtime using the version property.

Getting ready

To run this recipe, we will need a script that accesses phantom.version. The script in this recipe is available in the downloadable code repository as recipe01.js under chapter02. If we run the provided example script, we must change to the root directory for the book's sample code.

How to do it…

Consider the following script:

console.log('PhantomJS');
console.log('  - major version: ' + phantom.version.major);
console.log('  - minor version: ' + phantom.version.minor);
console.log('  - patch version: ' + phantom.version.patch);
phantom.exit();

Given the preceding script, enter the following at the command line:

phantomjs chapter02/recipe01.js

Our output should look like the following:

PhantomJS
  - major version: 1
  - minor version: 9
  - patch version...

Managing cookies with the phantom object

In this recipe, we will discuss how to work with cookies in PhantomJS. The phantom object exposes two properties (cookies and cookiesEnabled) and three methods (addCookie, clearCookie, and deleteCookie) that we can use to inspect and manipulate cookies at runtime.

Getting ready

To run this recipe, we may wish to run PhantomJS with persistent cookies using the cookies-file command-line argument.

The script in this recipe is available in the downloadable code repository as recipe02.js under chapter02. If we run the provided example script, we must change to the root directory for the book's sample code.

Lastly, the script in this recipe runs against the demo site that is included with the cookbook's sample code repository. To run the demo site, we must have Node.js installed. In a separate terminal, change to the phantomjs-sandbox directory (in the sample code's directory) and start the app with the following command:

node app.js

How to do...

Specifying a path for external scripts

In this recipe, we will introduce the libraryPath property on the phantom object and discuss how to use it to control the source of scripts that are loaded in the runtime via injectJs.

Getting ready

To run this recipe, we will need at least one injectable script and the script that we want to run.

The script in this recipe is available in the downloadable code repository as recipe03.js under chapter02. If we run the provided example script, we must change to the root directory for the book's sample code.

How to do it…

Consider the following script:

console.log('Initial libraryPath: ' + phantom.libraryPath);

phantom.libraryPath = phantom.libraryPath.replace(/chapter02$/,
  'lib');

console.log('Updated libraryPath: ' + phantom.libraryPath);

var isInjected = phantom.injectJs('hemingway.js');

if (isInjected) {
  console.log('Script was successfully injected.');
  console.log('Give me some...

Setting up a global PhantomJS error handler

This recipe introduces the onError callback and demonstrates how we can use it to catch and handle errors in the PhantomJS runtime. As this onError callback is attached to the phantom object, we can use it to handle errors that are not otherwise handled by try-catch statements in our PhantomJS scripts or by onError handlers attached to webpage objects.

Getting ready

To run this recipe, we will need a script that we believe has a tendency to fail.

The script in this recipe is available in the downloadable code repository as recipe04.js under chapter02. If we run the provided example script, we must change to the root directory for the book's sample code.

How to do it…

Consider the following script:

phantom.onError = function(message, trace) {
  console.error('[PHANTOMJS ERROR] ' + message);
  trace.forEach(function(t) {
    console.error('  >> [' + t.line + '] ' +
      (t.function ? '[' + t.function...

Introduction


PhantomJS exposes several core APIs to work with the headless browser and with the operating system that hosts the runtime. For example, we can get information about PhantomJS, inspect our host environment for values assigned to variables, and read from or write to the filesystem with the help of these APIs.

The recipes in this chapter will focus on those APIs that are considered part of the PhantomJS core. Specifically, we will introduce and discuss the global phantom object, the system and fs modules, and how to create and load our own CommonJS-compatible modules.

Inspecting the version at runtime


This recipe will introduce the global phantom object in PhantomJS and discuss how we can inspect the version at runtime using the version property.

Getting ready

To run this recipe, we will need a script that accesses phantom.version. The script in this recipe is available in the downloadable code repository as recipe01.js under chapter02. If we run the provided example script, we must change to the root directory for the book's sample code.

How to do it…

Consider the following script:

console.log('PhantomJS');
console.log('  - major version: ' + phantom.version.major);
console.log('  - minor version: ' + phantom.version.minor);
console.log('  - patch version: ' + phantom.version.patch);
phantom.exit();

Given the preceding script, enter the following at the command line:

phantomjs chapter02/recipe01.js

Our output should look like the following:

PhantomJS
  - major version: 1
  - minor version: 9
  - patch version: 2

How it works…

Our script operates by accessing...

Managing cookies with the phantom object


In this recipe, we will discuss how to work with cookies in PhantomJS. The phantom object exposes two properties (cookies and cookiesEnabled) and three methods (addCookie, clearCookie, and deleteCookie) that we can use to inspect and manipulate cookies at runtime.

Getting ready

To run this recipe, we may wish to run PhantomJS with persistent cookies using the cookies-file command-line argument.

The script in this recipe is available in the downloadable code repository as recipe02.js under chapter02. If we run the provided example script, we must change to the root directory for the book's sample code.

Lastly, the script in this recipe runs against the demo site that is included with the cookbook's sample code repository. To run the demo site, we must have Node.js installed. In a separate terminal, change to the phantomjs-sandbox directory (in the sample code's directory) and start the app with the following command:

node app.js

How to do it…

Consider the...

Specifying a path for external scripts


In this recipe, we will introduce the libraryPath property on the phantom object and discuss how to use it to control the source of scripts that are loaded in the runtime via injectJs.

Getting ready

To run this recipe, we will need at least one injectable script and the script that we want to run.

The script in this recipe is available in the downloadable code repository as recipe03.js under chapter02. If we run the provided example script, we must change to the root directory for the book's sample code.

How to do it…

Consider the following script:

console.log('Initial libraryPath: ' + phantom.libraryPath);

phantom.libraryPath = phantom.libraryPath.replace(/chapter02$/,
  'lib');

console.log('Updated libraryPath: ' + phantom.libraryPath);

var isInjected = phantom.injectJs('hemingway.js');

if (isInjected) {
  console.log('Script was successfully injected.');
  console.log('Give me some Fibonacci numbers! ' +
    fibonacci(Math.round(Math.random() * 10...

Setting up a global PhantomJS error handler


This recipe introduces the onError callback and demonstrates how we can use it to catch and handle errors in the PhantomJS runtime. As this onError callback is attached to the phantom object, we can use it to handle errors that are not otherwise handled by try-catch statements in our PhantomJS scripts or by onError handlers attached to webpage objects.

Getting ready

To run this recipe, we will need a script that we believe has a tendency to fail.

The script in this recipe is available in the downloadable code repository as recipe04.js under chapter02. If we run the provided example script, we must change to the root directory for the book's sample code.

How to do it…

Consider the following script:

phantom.onError = function(message, trace) {
  console.error('[PHANTOMJS ERROR] ' + message);
  trace.forEach(function(t) {
    console.error('  >> [' + t.line + '] ' +
      (t.function ? '[' + t.function + '] ' : '') +
      t.file || t.sourceURL);...

Controlling the exit status of a PhantomJS script


Although we have seen and used phantom.exit in all of our previous examples, we will now discuss it explicitly and learn in detail how it is used. In this recipe, we will learn how to control the exit status of the PhantomJS application.

Getting ready

To run this recipe, we require a script where we need to control the exit status.

The script in this recipe is available in the downloadable code repository as recipe05.js under chapter02. If we run the provided example script, we must change to the root directory for the book's sample code.

How to do it…

Consider the following script:

console.log('Running the PhantomJS exit demo...');

if (Math.floor(Math.random() * 10) % 2 === 0) {
  console.log('Exiting cleanly from PhantomJS!');
  phantom.exit();
} else {
  console.log('Exiting with an error status.');
  phantom.exit(1);
}

Given the preceding script, enter the following at the command line:

phantomjs chapter02/recipe05.js

If the script makes a...

Inspecting command-line arguments


In this recipe, we introduce the system module and discuss how to inspect arguments that are passed to the PhantomJS runtime environment from the command line. The system module is the bridge between PhantomJS, its host operating system, and the process it runs in.

Getting ready

To run this recipe, we will need a script that accepts arguments from the command line.

The script in this recipe is available in the downloadable code repository as recipe06.js under chapter02. If we run the provided example script, we must change to the root directory for the book's sample code.

How to do it…

Consider the following script:

var system = require('system'),
    args   = system.args;

console.log('script name is: ' + args[0]);

if (args.length > 1) {
  var restArgs = args.slice(1);
  restArgs.forEach(function(arg, i) {
    console.log('[' + (i + 1) + '] ' + arg);
  });
} else {
  console.log('No arguments were passed.');
}

phantom.exit();

Given the preceding script, enter...

Left arrow icon Right arrow icon

Description

A task-based guide that provides solutions to real-world test automation problems. This book is intended for web development professionals who want to integrate PhantomJS into their development and testing workflows. If you are a web developer looking to run automated unit tests while you work, or perhaps you are a QA engineer looking for a fast test automation utility, then this book is perfect for you. Some prior knowledge of JavaScript would be helpful.

What you will learn

  • Develop your own PhantomJS core modules
  • Learn sophisticated strategies for interacting with web page contents and how to capture those interactions
  • Create a frontend continuous integration (CI) strategy with PhantomJS
  • Perform unit testing with frameworks such as Jasmine, Mocha, and QUnit
  • Implement functional and endtoend testing with PhantomJS using tools such as Selenium, Capybara, and CasperJS
  • Automate performance analysis with libraries such as Confess.js and YSlow
  • Automate the generation of images and PDFs of your web content
Estimated delivery fee Deliver to Sweden

Premium delivery 7 - 10 business days

€17.95
(Includes tracking information)

Product Details

Country selected
Publication date, Length, Edition, Language, ISBN-13
Publication date : Jun 12, 2014
Length: 304 pages
Edition : 1st
Language : English
ISBN-13 : 9781783981922
Languages :
Concepts :
Tools :

What do you get with Print?

Product feature icon Instant access to your digital eBook copy whilst your Print order is Shipped
Product feature icon Paperback book shipped to your preferred address
Product feature icon Download this book in EPUB and PDF formats
Product feature icon Access this title in our online reader with advanced features
Product feature icon DRM FREE - Read whenever, wherever and however you want
Estimated delivery fee Deliver to Sweden

Premium delivery 7 - 10 business days

€17.95
(Includes tracking information)

Product Details

Publication date : Jun 12, 2014
Length: 304 pages
Edition : 1st
Language : English
ISBN-13 : 9781783981922
Languages :
Concepts :
Tools :

Packt Subscriptions

See our plans and pricing
Modal Close icon
€18.99 billed monthly
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Simple pricing, no contract
€189.99 billed annually
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just €5 each
Feature tick icon Exclusive print discounts
€264.99 billed in 18 months
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just €5 each
Feature tick icon Exclusive print discounts

Frequently bought together


Stars icon
Total 105.97
Getting Started with PhantomJS
€24.99
Mastering D3.js
€45.99
PhantomJS Cookbook
€34.99
Total 105.97 Stars icon

Table of Contents

9 Chapters
1. Getting Started with PhantomJS Chevron down icon Chevron up icon
2. PhantomJS Core Modules Chevron down icon Chevron up icon
3. Working with webpage Objects Chevron down icon Chevron up icon
4. Unit Testing with PhantomJS Chevron down icon Chevron up icon
5. Functional and End-to-end Testing with PhantomJS Chevron down icon Chevron up icon
6. Network Monitoring and Performance Analysis Chevron down icon Chevron up icon
7. Generating Images and Documents with PhantomJS Chevron down icon Chevron up icon
8. Continuous Integration with PhantomJS Chevron down icon Chevron up icon
Index Chevron down icon Chevron up icon

Customer reviews

Rating distribution
Full star icon Full star icon Full star icon Full star icon Half star icon 4.2
(5 Ratings)
5 star 40%
4 star 40%
3 star 20%
2 star 0%
1 star 0%
G.Lorrig Mar 14, 2018
Full star icon Full star icon Full star icon Empty star icon Empty star icon 3
Die Einführung in Phantomjs ist gut geschrieben, mit vielen leicht nachvollziehbaren Beispielen.Leider haben sich einige Dinge inzwischen verändert, manche Methoden sind nun in anderen Klassen verfügbar, was beim Nachvollziehen der Beispiele dann schon mal zu Frusterlebnissen führt.Eine aktualisierte Neuauflage wäre wünschenswert. Aber sie käme zu spät, ich habe das Buch schon gekauft. :D
Amazon Verified review Amazon
Jeffrey Pierce Oct 22, 2015
Full star icon Full star icon Full star icon Full star icon Full star icon 5
This book is exactly what you want in a cookbook. It is informative, concise and practical. Testing is usually an afterthought when it comes to JavaScript. This book, with its straight forward writing style, gives you many actionable ways to create a suite of tools which makes testing code not only easier, but enjoyable. I HIGHLY recommend this book to anyone who has an interest in learning more about analyzing and creating performant JavaScript applications.
Amazon Verified review Amazon
Angus Oct 30, 2014
Full star icon Full star icon Full star icon Full star icon Full star icon 5
This is much more than a cookbook, it's pretty much the bible of Phantom JS development.PhantomJS is remarkably thorough (a subtitle might be "no use-case left behind") and yet it's not at all intimidating. In fact the first two chapters are squarely aimed at the beginner. We're introduced to PhantomJS and its core modules with no assumptions re. experience, other than a basic command of JavaScript.From there Friesel takes us through unit testing (all mainstream frameworks are covered), integration testing, CI, using test data for performance metrics and rendering page content.Friesel's writing is clear and straightforward throughout. If you only get one PhantomJS book, get this one.
Amazon Verified review Amazon
Amazon Customer Jul 27, 2014
Full star icon Full star icon Full star icon Full star icon Empty star icon 4
I read one of the books’ recipes Automating performance analysis with YSlow and PhantomJS on the Packt website, and was thrilled when given the opportunity to review it.The first three chapters of this book explain how to get Phantom installed, use its core modules and begin working with webpages. The next four chapters cover specific use cases: unit, functional and performance testing and generating screenshots and documents. The final chapter describes how to setup Jenkins (the continuous integration server) to run your PhantomJS code.A couple of things stood out in this book:This book is not designed to be read straight through from cover to cover – like I did. Each of the recipes is designed to be self-contained (though this does lead to several paragraphs being repeated in most recipes – how to start the books demo site and run the example script). Making it easy to cherry pick the recipes that fit your needs and ignore those that don’t (i.e., the unit testing chapter contains recipes for running QUnit, Mocha and Jasmine tests – I doubt anyone is using all of these).The author clearly understands Phantom, both its strengths and weaknesses, at a very deep level. Several times he pointed out functions that lack documentation or where the documentation is incorrect. This type of information can save countless hours of debugging and frustration. Likewise, he clearly states where the use of an additional library (i.e., Casper) can make things simpler. When the reader may be left questioning how or why to use a specific recipe (i.e., Preventing CSS from downloading) he provides a clear and simple use case (to view the site when styles are disabled).The book makes the most of its cross references and external links. When a topic is introduced, but is outside the book’s scope the author provides a link to additional information (i.e., how to install Jenkins). Likewise, each recipe contains a “See also” section that references other recipes from the book, though in the eBook version not all of these were hyperlinked to the corresponding section. This was made worse by the fact that the table of contents only lists the chapter titles, not individual recipes, resulting in a lot of swiping to find the correct page.I did see a few minor issues:Deprecated code is not treated consistantly. In one instance (Running a PhantomJS script with arguments) phantom.args and phantom.scriptName provide the main functionality. The author notes that these functions are deprecated and their use therefore discouraged, and adding “Although using them for quick one-off exploratory scripts is fine, neither of these properties should go into any library that we intend to maintain or distribute. He also mentions the now preferred method of getting the same info using the system module. Which left me with several questions – why explore code using a method not suited to production? Why include the deprecated functions at all? Why not just rewrite the example to use the system module? However, when discussing the WebPage constructor he includes an example of the now deprecated form of the constructor noting that it should not be used, but was included because the reader may see it in older code. In my opinion this was a much better method of dealing with the issues presented by deprecated code.In the testing chapters I would have liked to have seen the results of the non-happy path (not all tests pass every time - if yours do your doing it wrong). What happens when the tests fail? Where can I get help interpreting the failure message? Are there online resources I can turn to like StackOverflow, a mailing list or IRC?I found it curious that when using Selenium the author chose to use the JAVA bindings and not the JS bindings – this may be a case of the author being more familiar with the java bindings, but since the book is based on a JS lib I would have thought that a better choice.In one recipe he suggests solving an error by deleting and reinstalling the node modules – but includes no discussion of why or how this solves the problem. While this will likely have no negative effects I still like to know why I am doing something.As I have said the recipes in this book are designed to be self-contained, in a handful of cases the author breaks from his pattern, most notably when using the confess.js library. He only discusses the config file after using it/mentioning it several times, making this information much harder to find.Overall the good far outweighs the bad in this book. For me the chapters on performance testing and continuous integration easily repaid the time invested in reading this book and implementing several of the book’s recipes.Since this book is not designed to be read from cover to cover, the question of value is a little harder to answer; but in the end, if you’re already using Phantom JS and are trying to maximize your return on investment, implementing only a couple of the book’s recipes should make it a worthwhile investment.
Amazon Verified review Amazon
Rodrigo Martin Jul 20, 2014
Full star icon Full star icon Full star icon Full star icon Empty star icon 4
http://www.packtpub.com/phantomjs-cookbook/book?utm_source=Mention.com&utm_medium=Blog%2FSM&utm_campaign=MarketingThe PhantomJS Cookbook starts explaining the basics of PhantomJS.Later on, a set of recipes explains the core modules.How to interact with webpage objects comes next, including http actions, injecting js into the browser, simulationuf user input actions, web sockets and an interesting way of blocking css from downloading, amongst others.Then we are presented with how to drive unit tests usign PhantomJS as the main driver, with recipes for a wideset of technologies: jasmine, karma, qunit, grunt for tasks automation. It also presents how to integrate with codecoverage reports tool like Istanbul.The reading continues with Functional and end-to-end testing recipes, with Selenium, GhostDriver, Poltergeist, CapybaraCasper JS, just to name some of them. I've found the ideas for the recipes on how to perform visual regressions usingPhantomCSS very useful.The latest chapters provides good examples for Network monitoring and Performance Analysis, generation of images anddocuments for the reporting part of your testing and development efforts, and finally how to seamessly integratePhantomJS with your CI server.I would recommend this book to readers who wants to dig in how to integrate headless testing to your currentbattery of automated tests. It also explains other concepts, besides PhantomJS, that adds value to the overall proposalof this publication.One little note, though, is the repetition on all the chapters of how to start the example application. Please refactor! :P
Amazon Verified review Amazon
Get free access to Packt library with over 7500+ books and video courses for 7 days!
Start Free Trial

FAQs

What is the delivery time and cost of print book? Chevron down icon Chevron up icon

Shipping Details

USA:

'

Economy: Delivery to most addresses in the US within 10-15 business days

Premium: Trackable Delivery to most addresses in the US within 3-8 business days

UK:

Economy: Delivery to most addresses in the U.K. within 7-9 business days.
Shipments are not trackable

Premium: Trackable delivery to most addresses in the U.K. within 3-4 business days!
Add one extra business day for deliveries to Northern Ireland and Scottish Highlands and islands

EU:

Premium: Trackable delivery to most EU destinations within 4-9 business days.

Australia:

Economy: Can deliver to P. O. Boxes and private residences.
Trackable service with delivery to addresses in Australia only.
Delivery time ranges from 7-9 business days for VIC and 8-10 business days for Interstate metro
Delivery time is up to 15 business days for remote areas of WA, NT & QLD.

Premium: Delivery to addresses in Australia only
Trackable delivery to most P. O. Boxes and private residences in Australia within 4-5 days based on the distance to a destination following dispatch.

India:

Premium: Delivery to most Indian addresses within 5-6 business days

Rest of the World:

Premium: Countries in the American continent: Trackable delivery to most countries within 4-7 business days

Asia:

Premium: Delivery to most Asian addresses within 5-9 business days

Disclaimer:
All orders received before 5 PM U.K time would start printing from the next business day. So the estimated delivery times start from the next day as well. Orders received after 5 PM U.K time (in our internal systems) on a business day or anytime on the weekend will begin printing the second to next business day. For example, an order placed at 11 AM today will begin printing tomorrow, whereas an order placed at 9 PM tonight will begin printing the day after tomorrow.


Unfortunately, due to several restrictions, we are unable to ship to the following countries:

  1. Afghanistan
  2. American Samoa
  3. Belarus
  4. Brunei Darussalam
  5. Central African Republic
  6. The Democratic Republic of Congo
  7. Eritrea
  8. Guinea-bissau
  9. Iran
  10. Lebanon
  11. Libiya Arab Jamahriya
  12. Somalia
  13. Sudan
  14. Russian Federation
  15. Syrian Arab Republic
  16. Ukraine
  17. Venezuela
What is custom duty/charge? Chevron down icon Chevron up icon

Customs duty are charges levied on goods when they cross international borders. It is a tax that is imposed on imported goods. These duties are charged by special authorities and bodies created by local governments and are meant to protect local industries, economies, and businesses.

Do I have to pay customs charges for the print book order? Chevron down icon Chevron up icon

The orders shipped to the countries that are listed under EU27 will not bear custom charges. They are paid by Packt as part of the order.

List of EU27 countries: www.gov.uk/eu-eea:

A custom duty or localized taxes may be applicable on the shipment and would be charged by the recipient country outside of the EU27 which should be paid by the customer and these duties are not included in the shipping charges been charged on the order.

How do I know my custom duty charges? Chevron down icon Chevron up icon

The amount of duty payable varies greatly depending on the imported goods, the country of origin and several other factors like the total invoice amount or dimensions like weight, and other such criteria applicable in your country.

For example:

  • If you live in Mexico, and the declared value of your ordered items is over $ 50, for you to receive a package, you will have to pay additional import tax of 19% which will be $ 9.50 to the courier service.
  • Whereas if you live in Turkey, and the declared value of your ordered items is over € 22, for you to receive a package, you will have to pay additional import tax of 18% which will be € 3.96 to the courier service.
How can I cancel my order? Chevron down icon Chevron up icon

Cancellation Policy for Published Printed Books:

You can cancel any order within 1 hour of placing the order. Simply contact customercare@packt.com with your order details or payment transaction id. If your order has already started the shipment process, we will do our best to stop it. However, if it is already on the way to you then when you receive it, you can contact us at customercare@packt.com using the returns and refund process.

Please understand that Packt Publishing cannot provide refunds or cancel any order except for the cases described in our Return Policy (i.e. Packt Publishing agrees to replace your printed book because it arrives damaged or material defect in book), Packt Publishing will not accept returns.

What is your returns and refunds policy? Chevron down icon Chevron up icon

Return Policy:

We want you to be happy with your purchase from Packtpub.com. We will not hassle you with returning print books to us. If the print book you receive from us is incorrect, damaged, doesn't work or is unacceptably late, please contact Customer Relations Team on customercare@packt.com with the order number and issue details as explained below:

  1. If you ordered (eBook, Video or Print Book) incorrectly or accidentally, please contact Customer Relations Team on customercare@packt.com within one hour of placing the order and we will replace/refund you the item cost.
  2. Sadly, if your eBook or Video file is faulty or a fault occurs during the eBook or Video being made available to you, i.e. during download then you should contact Customer Relations Team within 14 days of purchase on customercare@packt.com who will be able to resolve this issue for you.
  3. You will have a choice of replacement or refund of the problem items.(damaged, defective or incorrect)
  4. Once Customer Care Team confirms that you will be refunded, you should receive the refund within 10 to 12 working days.
  5. If you are only requesting a refund of one book from a multiple order, then we will refund you the appropriate single item.
  6. Where the items were shipped under a free shipping offer, there will be no shipping costs to refund.

On the off chance your printed book arrives damaged, with book material defect, contact our Customer Relation Team on customercare@packt.com within 14 days of receipt of the book with appropriate evidence of damage and we will work with you to secure a replacement copy, if necessary. Please note that each printed book you order from us is individually made by Packt's professional book-printing partner which is on a print-on-demand basis.

What tax is charged? Chevron down icon Chevron up icon

Currently, no tax is charged on the purchase of any print book (subject to change based on the laws and regulations). A localized VAT fee is charged only to our European and UK customers on eBooks, Video and subscriptions that they buy. GST is charged to Indian customers for eBooks and video purchases.

What payment methods can I use? Chevron down icon Chevron up icon

You can pay with the following card types:

  1. Visa Debit
  2. Visa Credit
  3. MasterCard
  4. PayPal
What is the delivery time and cost of print books? Chevron down icon Chevron up icon

Shipping Details

USA:

'

Economy: Delivery to most addresses in the US within 10-15 business days

Premium: Trackable Delivery to most addresses in the US within 3-8 business days

UK:

Economy: Delivery to most addresses in the U.K. within 7-9 business days.
Shipments are not trackable

Premium: Trackable delivery to most addresses in the U.K. within 3-4 business days!
Add one extra business day for deliveries to Northern Ireland and Scottish Highlands and islands

EU:

Premium: Trackable delivery to most EU destinations within 4-9 business days.

Australia:

Economy: Can deliver to P. O. Boxes and private residences.
Trackable service with delivery to addresses in Australia only.
Delivery time ranges from 7-9 business days for VIC and 8-10 business days for Interstate metro
Delivery time is up to 15 business days for remote areas of WA, NT & QLD.

Premium: Delivery to addresses in Australia only
Trackable delivery to most P. O. Boxes and private residences in Australia within 4-5 days based on the distance to a destination following dispatch.

India:

Premium: Delivery to most Indian addresses within 5-6 business days

Rest of the World:

Premium: Countries in the American continent: Trackable delivery to most countries within 4-7 business days

Asia:

Premium: Delivery to most Asian addresses within 5-9 business days

Disclaimer:
All orders received before 5 PM U.K time would start printing from the next business day. So the estimated delivery times start from the next day as well. Orders received after 5 PM U.K time (in our internal systems) on a business day or anytime on the weekend will begin printing the second to next business day. For example, an order placed at 11 AM today will begin printing tomorrow, whereas an order placed at 9 PM tonight will begin printing the day after tomorrow.


Unfortunately, due to several restrictions, we are unable to ship to the following countries:

  1. Afghanistan
  2. American Samoa
  3. Belarus
  4. Brunei Darussalam
  5. Central African Republic
  6. The Democratic Republic of Congo
  7. Eritrea
  8. Guinea-bissau
  9. Iran
  10. Lebanon
  11. Libiya Arab Jamahriya
  12. Somalia
  13. Sudan
  14. Russian Federation
  15. Syrian Arab Republic
  16. Ukraine
  17. Venezuela