-
Let the automation in!
-
What?
-
might
- Logs processing
-
should
-
End-to-end functional tests
- API
- UI
- Business critical checks
- Test data setup
-
must
- Environment setting
- Routines
- When?
-
Environment setup automation
-
Tools:
- SSH, Kitty
- Console text editing: vim, nano
-
*nix shell scripting
/ it’s variant for Windows: Cygwin
-
OS and FS
- permissions
-
Listing files
- ls
- Copying, moving, creating folders/files
- Disk space
- htop and processes management
- grep
- permissions
- | > sed
- *.sh files: creating and executing
-
Databases: SQL
- select
- join
-
Python as a scripting tool
- Installation: pip, packages
- iPython - interactive command line
- Log file processing
- Simple results reporting
-
Web ent-to-end functional testing
-
IDE
- Pycharm
-
API:
-
REST
- JSON
- POST, PUT, GET, DELETE
-
SOAP
- XML and WSDL
- with SOAP UI
- with Python
-
UI:
- Selenium IDE
-
Webdriver
-
with Python and pytest:
- pytest-variables
- pytest-html
- pytest- selenium
- Page object pattern
-
Semi-automation steps
-
strings
- big-list-of-naughty-strings
-
Bugmagnet
- with your own config
-
Selenium IDE
- Record/playback “magic”
- It’s problems
- DOM
- Locators
- Tools to identify locator: Firepath,
- Bookmarklets
- Notepad++
-
Mobile testing
- Network Latency / Packet Loss
- Parallel Connections
- Testing in Real Environments and Users
- Background Activity
- Updates