search

aiden / autobot

A Multi-Platform Bot Testing Framework Designed for Humans
MIT License
47 stars 15 forks source link

Versioning of test files #3

Open ginccc opened 7 years ago

ginccc commented 7 years ago

Imagining you develop a chatbot v1, then a chatbot v2.. obviously the bot scripts will evolve. ideally, v1 can be tested with v1 tests (e.g. production), while v2 bot can be tested with v2 tests without screwing up the tests of v1.

How would you do that? Or is that even easily possible without copy/paste the entire test suit?

lingz commented 7 years ago

So to be more specific, do you mean given a set of tests, some tests should only be run for the v1 api, some should be run for the v2 api, and some should be run for both apis?

ginccc commented 7 years ago

let me formulate it as a user story: As developer, I would like to further develop exiting tests, without altering current test, that reflect functionality of the current version, but at the same time not need to copy paste the whole bunch of tests for v2

similarly to versioning of libraries

lingz commented 6 years ago

Oh sorry just came back to this one. What we do is we check our autobot tests into our repo, so that they are always up to date with the version of code. So we just version with github.