Integration tests test multiple components together by using dependencies like databases, services, and APIs. They are useful for testing typical workflows and ensuring components interact smoothly but can be hard to write, maintain, and localize errors. UI tests with Selenium automate interactions with a web application like users do in order to detect errors not found by other test types, but take more time and setup compared to unit tests.

1. eleks.comeleks.com
Integration testing
And UI testing (Selenium Web driver)

2. Tests can be different

3. Integration tests features
Test several components together
Use dependencies (DB, Services, API, FS, AD, ...)
Can have different behavior
Require configuration
Results can be different (depend on environment, order of
execution, multithreading, phase of Moon).

4. Integration tests features
Following code can often be seen in integration tests
File.Open(...)
Connection.Close(...)
Environment.MachineName
DateTime.Now
TearDown(...)

5. Integration tests “Pro’s”
Pro’s:
Make sure nuts and bolts fit together
Make sure software stack components interact smoothly
Test behavior and infrastructure (tested code)/test % is high
Reflect typical workflows

6. Integration tests “Con’s”
Con’s:
Large time investment
Hard to test all critical paths
Harder to localize source of errors
Harder to write and maintain

7. Project structure
Unit and integration tests
should be separated
Common practice is to end
up project name with “.Tests”
suffix

8. eleks.comeleks.com
Show me the code!
[integration test examples]

9. eleks.comeleks.com
UI testing
Testing Web apps using Selenium

10. Wait, UI?
Web Apps are Heterogeneous systems at most
Different technology stacks for backend
Complex multi-layer and multi-tier systems
Should test all involved parts
Can’t directly test server code and SQL
Everything can go wrong...

11. Front end test features
Pros:
Hide the complexity of a backend
Tests can reproduce exactly what users do
Can detect errors not visible by other types of tests
UI tests can be utilized for any automation in general

12. Front end test features
Cons:
Execution time
Third party tools/environments
Hard to maintain
Complexity
Dynamic pages

13. What is it?
Selenium is a Functional Automation tool for Web apps
Works with different languages, browsers, Oses etc.
Interacts with Web app via UI

14. What is my options?
Selenium 2 (Selenium Web Driver)
Selenium 1 (Selenium RC)
Selenium IDE
Selenium-Grid
More details at: http://docs.seleniumhq.org/docs/01_introducing_selenium.jsp

15. Selenium Web Driver
Interactions via DRIVERs
Various drivers are supported:
Chrome driver, Opera driver, Android driver, IOS driver

16. UI Test key parts
Start driver
IWebDriver driver = new FirefoxDriver();
Navigate to desired page
driver.Navigate().GoToUrl(“...”);
Find controls for interaction
var elem = driver.FindElement(By.Name(“...”));
Act
elem.SendKeys(“Ok, Google”);

17. UI Test key parts
Wait
/* WebDriverWait is preferred, but Thread.Sleep
will also work*/
Assert
something.Should.Be(...);
Exit/Clean up
driver.Close();

18. Selenium API
Easy to find controls/tags
By name, id, css, xpath etc.
Easy to navigate
Select active window
Switch to url
Easy integrates with NUnit
No need for installers, manual process running etc

19. eleks.comeleks.com
UI automated tests example
[Asp.Net 5 + NUnit + Selenium WebDriver]

20. It’s time to practice