Testing meeting with Caleb

[bdavey07]

Met with Caleb Enterprise Applications to discuss testing strategies. We described our test driven development strategy and showed off TestCafe.

What Caleb is doing now

• [x] Researching Testing in TFS
• [x] Creating a working Proof of Concept
• [ ] Getting the rest of the team on board

Caleb's Test Structure

• Test plans: a group of test cases much like our feature files
  • Ex: How a student uses WebAdvisor
• Test cases: individual testable item in the test plan
  • Can be a unit test or functional test
  • Ex: Student can view class schedule
• Test run: Saved in TFS, the data from each time a test plan runs
  • Includes nice graphs and such

The test implementation

• Done in MSTest
  • Can keep track of manual and automated tests in the Test runs
• Action Recording
  • Records user clicking through browser and making assertions
  • Creates test files that are not easily editable
  • Can only be done in IE
• Coded UI
  • Essentially TestCafe in C#
  • Has extensions to work with Chrome and Firefox
  • Those extensions are broken (and have been for 8 months)
• Ranorex
  • Same idea as Action Recording
  • Works in it's own IDE
  • Can edit files it creates
  • Works with multiple browsers
• Large and Complex dependency chain
  • TFS builds MSTest
  • MSTest hosts Coded UI tests (a test file in MSTests)
  • The Coded UI tests call the Ranorex tests
  • Ranorex tests return pass/fail to the Coded UI tests
  • The Coded UI tests report to MSTest
  • MSTest report back to TFS

Takeaways from Caleb

• EA is all in with TFS
• Everything is in C#
• TFS collects test runs with nice graphs and data, something we should look into implementing

@nevantan feel free to add anything I missed here