I don't work in the game industry, but maybe these books can help you out.

Books

• Break Into The Game Industry: How to Get A Job Making Video Games
  
• How to Score Your First Game Job: And What to Expect from the Videogame Industry
  
• Breaking Into the Game Industry: Advice for a Successful Career from Those Who Have Done It
  
• How to Get a Job in Video Games
  
• Get in the Game: Careers in the Game Industry
  
• How to Become a Video Game Artist: The Insider's Guide to Landing a Job in the Gaming World
  
• Land a Job as a Video Game Tester
  
• Beginner's Guide (Video Game Careers Book 1)
  
• VGC Ultimate Edition (Video Game Careers) (Volume 4)
  
• Inside the Video Game Industry : Game Developers Talk About the Business of Play
  
• Video Games: An Introduction to the Industry
  
• The Video Game Industry: Formation, Present State, and Future
  
  Articles
  
  
• How to get into the games industry – an insiders' guide
  
• Game Developers, what is getting into the gaming industry really like?
  
  Videos
  
  
• Top 10 Tips for Getting Into The Video Game Industry
  
• "How does a person get a job at your videogame company?"
  
• What's it's really like to work in Game industry
  
  Edit: Added more things to read and watch.

I've posted this before but I'll repost it here:

Now in terms of the question that you ask in the title - this is what I recommend:

Job Interview Prep

1. Cracking the Coding Interview: 189 Programming Questions and Solutions
   
2. Programming Interviews Exposed: Coding Your Way Through the Interview
   
3. Introduction to Algorithms
   
4. The Algorithm Design Manual
   
5. Effective Java
   
6. Concurrent Programming in Java™: Design Principles and Pattern
   
7. Modern Operating Systems
   
8. Programming Pearls
   
9. Discrete Mathematics for Computer Scientists
   
   

   Junior Software Engineer Reading List
   

   
   

   Read This First
   

   
   

10. Pragmatic Thinking and Learning: Refactor Your Wetware
    
    

    Fundementals
    

    
    

11. Code Complete: A Practical Handbook of Software Construction
    
12. Software Estimation: Demystifying the Black Art
    
13. Software Engineering: A Practitioner's Approach
    
14. Refactoring: Improving the Design of Existing Code
    
15. Coder to Developer: Tools and Strategies for Delivering Your Software
    
16. Perfect Software: And Other Illusions about Testing
    
17. Getting Real: The Smarter, Faster, Easier Way to Build a Successful Web Application
    
    

    Understanding Professional Software Environments
    

    
    

18. Agile Software Development: The Cooperative Game
    
19. Software Project Survival Guide
    
20. The Best Software Writing I: Selected and Introduced by Joel Spolsky
    
21. Debugging the Development Process: Practical Strategies for Staying Focused, Hitting Ship Dates, and Building Solid Teams
    
22. Rapid Development: Taming Wild Software Schedules
    
23. Peopleware: Productive Projects and Teams
    
    

    Mentality
    

    
    

24. Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency
    
25. Against Method
    
26. The Passionate Programmer: Creating a Remarkable Career in Software Development
    
    

    History
    

    
    

27. The Mythical Man-Month: Essays on Software Engineering
    
28. Computing Calamities: Lessons Learned from Products, Projects, and Companies That Failed
    
29. The Deadline: A Novel About Project Management
    
    

    Mid Level Software Engineer Reading List
    

    
    

    Read This First
    

    
    

30. Personal Development for Smart People: The Conscious Pursuit of Personal Growth
    
    

    Fundementals
    

    
    

31. The Clean Coder: A Code of Conduct for Professional Programmers
    
32. Clean Code: A Handbook of Agile Software Craftsmanship
    
33. Solid Code
    
34. Code Craft: The Practice of Writing Excellent Code
    
35. Software Craftsmanship: The New Imperative
    
36. Writing Solid Code
    
    

    Software Design
    

    
    

37. Head First Design Patterns: A Brain-Friendly Guide
    
38. Design Patterns: Elements of Reusable Object-Oriented Software
    
39. Domain-Driven Design: Tackling Complexity in the Heart of Software
    
40. Domain-Driven Design Distilled
    
41. Design Patterns Explained: A New Perspective on Object-Oriented Design
    
42. Design Patterns in C# - Even though this is specific to C# the pattern can be used in any OO language.
    
43. Refactoring to Patterns
    
    

    Software Engineering Skill Sets
    

    
    

44. Building Microservices: Designing Fine-Grained Systems
    
45. Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools
    
46. NoEstimates: How To Measure Project Progress Without Estimating
    
47. Object-Oriented Software Construction
    
48. The Art of Software Testing
    
49. Release It!: Design and Deploy Production-Ready Software
    
50. Working Effectively with Legacy Code
    
51. Test Driven Development: By Example
    
    

    Databases
    

    
    

52. Database System Concepts
    
53. Database Management Systems
    
54. Foundation for Object / Relational Databases: The Third Manifesto
    
55. Refactoring Databases: Evolutionary Database Design
    
56. Data Access Patterns: Database Interactions in Object-Oriented Applications
    
    

    User Experience
    

    
    

57. Don't Make Me Think: A Common Sense Approach to Web Usability
    
58. The Design of Everyday Things
    
59. Programming Collective Intelligence: Building Smart Web 2.0 Applications
    
60. User Interface Design for Programmers
    
61. GUI Bloopers 2.0: Common User Interface Design Don'ts and Dos
    
    

    Mentality
    

    
    

62. The Productive Programmer
    
63. Extreme Programming Explained: Embrace Change
    
64. Coders at Work: Reflections on the Craft of Programming
    
65. Facts and Fallacies of Software Engineering
    
    

    History
    

    
    

66. Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software
    
67. New Turning Omnibus: 66 Excursions in Computer Science
    
68. Hacker's Delight
    
69. The Alchemist
    
70. Masterminds of Programming: Conversations with the Creators of Major Programming Languages
    
71. The Information: A History, A Theory, A Flood
    
    

    Specialist Skills
    

    
    In spite of the fact that many of these won't apply to your specific job I still recommend reading them for the insight, they'll give you into programming language and technology design.
    
    

72. Peter Norton's Assembly Language Book for the IBM PC
    
73. Expert C Programming: Deep C Secrets
    
74. Enough Rope to Shoot Yourself in the Foot: Rules for C and C++ Programming
    
75. The C++ Programming Language
    
76. Effective C++: 55 Specific Ways to Improve Your Programs and Designs
    
77. More Effective C++: 35 New Ways to Improve Your Programs and Designs
    
78. More Effective C#: 50 Specific Ways to Improve Your C#
    
79. CLR via C#
    
80. Mr. Bunny's Big Cup o' Java
    
81. Thinking in Java
    
82. JUnit in Action
    
83. Functional Programming in Scala
    
84. The Art of Prolog: Advanced Programming Techniques
    
85. The Craft of Prolog
    
86. Programming Perl: Unmatched Power for Text Processing and Scripting
    
87. Dive into Python 3
    
88. why's (poignant) guide to Ruby

For a book that provides both a good introduction to testing terminology and concepts, as well as a fair amount of practical/instructional examples, I really like Software Testing: Fundamental Principles and Essential Knowledge. Also, I'm not sure whether you're wondering about getting started doing QA for your own games, or getting a job at a game company. If the latter, I'd say that the best way to get started depends on what your goals are:

• If your ultimate goal is to move into a different type of role within the game industry, simply being in the right place at the right time (i.e., an area that has at least a few game companies, during the time when people are hiring testers to get their games in shape for pre-holiday ship dates) and demonstrating that you are a mature and dependable person with good computer skills and a knowledge of basic testing principles may be sufficient. While you're working in an entry-level test role, keep on improving the relevant skills for the type of job you hope to eventually have, and then apply for one of those openings within the company when you're ready. Caveat: this is much more likely to happen at a small to medium-sized game company than at one of the major ones, where entry-level testers are often segregated completely from any development, art, or production people. At small companies, though, I've seen numerous instances of people who started off in manual tester positions while they were in college or otherwise improving their skills eventually move up into art or coding roles.
  
  
• If your eventual goal is to end up at a higher-level testing role within the game industry-- SDET, QA Manager/Lead, etc.-- one thing that can help is starting your career outside of games. My first job out of college was at a company that made medical software; I was able to get some real-world coding, testing, and planning experience, and then managed to skip the entry-level game testing jobs and move directly into higher-level test roles. A lot of other SDETs I've worked with in games have had a similar career path, and I've seen a lot of people with an eventual desire to be SDETs or leads get stuck in more entry-level testing roles when a black box game testing job was their first role within the game industry. I'm not quite sure why this is the case, but this is definitely something I've observed.
  
  Sorry for the tl;dr, and I hope this helps! If you have any questions about things like finding and applying for QA jobs, I'd be more than happy to answer them.

Here you go

http://www.amazon.com/Testing-Scala-Daniel-Hinojosa/dp/1449315119/ref=sr_1_1?ie=UTF8&qid=1464995693&sr=8-1&keywords=scala+testing

Selenium WebDriver, mostly. It's a defacto standard now.

Don't tie yourself to python though, test automation tends to be in the same language as the actual product. Or you'll be brought on to maintain and enhance an existing testing framework. Getting to be there when the decisions are made as to what to use is a rare opportunity.

There are a lot of people doing test automation through protractor (node.js), but also python, ruby, java, go ... basically if someone used it to make a web framework, someone also made a web testing framework for it.

> what other skills I'll need

Testing is really its own discipline within software development. You could read this book, if you've got the time: A Friendly Introduction to Software Testing

(Test automation is what I do for a living, 15+ years now)

Honestly, not really. I've got copies of both The Cucumber Book and The Rspec Book and both are alright, but both are more than likely pretty much out of date. If you're looking for syntax, I'd just suggest reading the documentation for the relevant libraries.

I've heard okay/good things about Rails Test Prescriptions but haven't personally read it.

I have a few blog posts that I enjoy:

• http://mrjoy.com/2013/09/19/an-unusual-case-for-cucumber/
  
• http://collectiveidea.com/blog/archives/2010/09/13/practical-cucumber-organization/
  
• http://collectiveidea.com/blog/archives/2010/09/08/practical-cucumber-scenario-specific-steps/
  
• http://robots.thoughtbot.com/how-we-test-rails-applications (but I don't write Controller/View specs, instead testing those via feature tests)
  
  I've personally learned a non-trivial amount of testing methodology/principles in Ruby from Avdi Grimm, particularly:
  
  
• the multi-part stretches of RubyTapas (e.g. Gem-Love, PulseFFI)
  
• The Making of Cowsays
  
• Objects on Rails

Hi, I don't know a lot of such resources. I had read only one book about mobile testing - https://www.amazon.com/Hands-Mobile-App-Testing-Involved/dp/0134191714 - it's not bad especially if you are beginner.

Cool, you will probably find these books to be useful (as I did): Professional C++, 3rd edition and Effective Modern C++

Yeah I have read around 70%-80% of all YDKJS books combined .

By the way just in any case you find anything interesting and helpful (but for also copy pasting this list in the future) here are the books-site tutorials-docs that I am reading-have read-plan to read-follow :

web dev road map

htmldog

www.javascript.info

css in depth (manning)

eloquent js

YDKJS (all books)

HTML5 for masterminds

dom enlightenment

high performance images

web performance in action

reliable javascript

building progressive web apps

http: the definitive guide

learning http 2

cracking the coding interview

javascript data structure and algorithms (be careful,not a good choice, it has a lot of mistakes but I find it concise)

professional git

vs code docs

Using SVG with CSS3 and HTML5

Interactive Data Visualization for the Web

refactoring ui

figma docs

react docs

redux docs

vue docs

webpack docs

clean code

design patterns

web components in action

Inkscape: Guide to a Vector Drawing Program

and many more to come .

You can find complete Java code for this problem in this book:
http://www.amazon.com/Mastering-Selenium-WebDriver-Mark-Collin/dp/1784394351