Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Test Script and add to project #234

Open
ogmage78 opened this issue Apr 11, 2017 · 3 comments
Open

Create Test Script and add to project #234

ogmage78 opened this issue Apr 11, 2017 · 3 comments

Comments

@ogmage78
Copy link
Contributor

As each of us is working on different parts at different times, it would be useful to have a document like our read me or change log where we could put tests and expected results for our areas. That way prior to submitting a PR you could run through the test to make sure your change did not break the world.

Quick example: Test item pickup and drop

  1. Log in on 2 characters ( we need to test what other clients are seeing)
  2. On client 1 in the chat window type @ctw me
  3. Take the wand and drop it to the ground.
    a. Did both clients see and here the drop? Do you see the wand on the ground from both clients. Did client 1 do the animation to set the wand on the ground. Is the item out of the backpack for client 1?
  4. Pick up the wand. Is the wand gone for client 2 and in the backpack of client 1. Did you see the animation from both clients. Did you hear the pickup sound.
@Mag-nus
Copy link
Member

Mag-nus commented Dec 4, 2017

I think this would be best done by a vtank/mag-tools meta.

We could host the meta in the repo to maintain version history. This would also be a great way to get meta writers involved in ACE.

@gmriggs
Copy link
Collaborator

gmriggs commented Aug 17, 2018

These should be handled by automated tests imo

@jamesmcmenamin
Copy link

Automated tests are the way to go but cant really argue with having a side by side of actual smoke testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants