Frequently Asked Questions

Attention

This documentation is deprecated and should no longer be used.

Please, check the new documentation at https://altwalker.github.io/altwalker/, which is being actively maintained.

Also note that all projects related to AltWalker were moved from GitLab to GitHub, you can find the new projects at https://github.com/altwalker.

What’s the difference between AltWalker and GraphWalker?

TL;DR: AltWalker is a wrapper for GraphWalker that adds support for running tests written in Python3 and C#/.NET.

GraphWalker is an Model-Based Testing tool. It reads models in the shape of directed graphs, generates (tests) paths from these graphs and supports running tests in written in Java.

AltWalker is a test runner it uses GraphWalker for path generation and adds support for generating and running tests written in Python3 and C#/.NET with the option of adding support for other languages (by writing your own executor).

Can I use Appium/Selenium with AltWalker?

Yes, AltWalker does not interact with your SUT (System Under Test). You need some other tool to do that. If, for instance, you want to test a web application, you would perhaps use Selenium to do that, or if your target is a mobile app, then Appium might be your choice.

How to reuse the same method for two (or more) elements?

If you add two (or more) elements with the same name (but different id) in your model, both elements will be mapped to the same method.

You can use this technique for actions that can happen on different states of the application. For example an e_go_back edge that will press the back button from multiple pages.