Test Case Recorder #87

brxck · 2021-07-08T19:29:46Z

This is the test case recorder for #59

Adds a command which records info about the next cursorless command and saves it to a yaml fixture:

talonCommand: swap harp with crunch
command:
  actionName: swap
  partialTargets:
    - type: primitive
      mark:
        type: decoratedSymbol
        symbolColor: default
        character: h
    - type: primitive
      mark:
        type: decoratedSymbol
        symbolColor: default
        character: k
  extraArgs: []
languageId: python
targets:
  - type: primitive
    mark:
      type: decoratedSymbol
      symbolColor: default
      character: h
    selectionType: token
    position: contents
    modifier:
      type: identity
    insideOutsideType: inside
  - type: primitive
    mark:
      type: decoratedSymbol
      symbolColor: default
      character: k
    selectionType: token
    position: contents
    modifier:
      type: identity
    insideOutsideType: inside
marks:
  default.h:
    start:
      line: 3
      character: 12
    end:
      line: 3
      character: 17
  default.k:
    start:
      line: 2
      character: 22
    end:
      line: 2
      character: 27
initialState:
  document: |
    import sys

    def hello_world(name="pokey"):
        print(f"hello, {name}")
      
    if __name__ == "__main__":
        hello_world(sys.argv[0])
  selections:
    - active:
        line: 7
        character: 0
      anchor:
        line: 7
        character: 0
  visibleRanges: []
  clipboard: ""
  thatMark: []
finalState:
  document: |
    import sys

    def hello_world(name="hello"):
        print(f"pokey, {name}")
      
    if __name__ == "__main__":
        hello_world(sys.argv[0])
  selections:
    - active:
        line: 7
        character: 0
      anchor:
        line: 7
        character: 0
  visibleRanges: []
  clipboard: ""
  thatMark:
    - active:
        line: 3
        character: 17
      anchor:
        line: 3
        character: 12
    - active:
        line: 2
        character: 27
      anchor:
        line: 2
        character: 22
returnValue: null

On recording the user is prompted for the talon command and test fixture file nam

During testing the editor initial state is restored, the recorded command is run, and the result is compared to the recorded one.

pokey · 2021-07-08T20:46:11Z

Great! Would be super helpful to paste an example snapshot yaml into a comment to give a sense of what it looks like

brxck · 2021-07-08T20:56:53Z

Sure thing!

command:
  actionName: swap
  partialTargets:
    - type: primitive
      mark:
        type: decoratedSymbol
        symbolColor: default
        character: h
    - type: primitive
      mark:
        type: decoratedSymbol
        symbolColor: default
        character: p
  extraArgs: []
languageId: typescript
decorations:
  default.h:
    start:
      line: 1
      character: 15
    end:
      line: 1
      character: 20
  default.p:
    start:
      line: 4
      character: 12
    end:
      line: 4
      character: 17
initialState:
  document: |
    function helloWorld(name: string) {
      console.log(`hello, ${name}`)
    }

    helloWorld("pokey")
  selections:
    - active: &ref_0
        _line: 5
        _character: 0
      anchor: &ref_1
        _line: 5
        _character: 0
  visibleRanges:
    - start:
        line: 0
        character: 0
      end:
        line: 5
        character: 0
finalState:
  document: |
    function helloWorld(name: string) {
      console.log(`pokey, ${name}`)
    }

    helloWorld("hello")
  selections:
    - active: *ref_0
      anchor: *ref_1
  visibleRanges:
    - start:
        line: 0
        character: 0
      end:
        line: 5
        character: 0

And I already see that I should probably look into serializing values instead of the references for snapshot selections 🧐

pokey · 2021-07-08T21:12:24Z

Dude. This. Is. Epic. 😍

pokey · 2021-07-08T21:12:53Z

Looks great in yaml. Love how the it uses that block for the doc text. Super readable

pokey · 2021-07-08T21:14:44Z

Gonna save us so much time writing test cases

brxck · 2021-07-10T23:44:48Z

Now able to run some test cases. Plenty to improve here, including the fact that cases with inferred targets seem to throw an error...

For example,

this line

function transformSelection(
  context: ProcessedTargetsContext,
  target: PrimitiveTarget,
  selection: SelectionWithEditor
): { selection: SelectionWithEditor; context: SelectionContext }[] {
  const { transformation } = target;

  switch (transformation.type) {
    case "identity":
      return [{ selection, context: {} }];
    case "containingScope":
      var node: SyntaxNode | null = context.getNodeAtLocation( // !!!
        new vscode.Location(selection.editor.document.uri, selection.selection)
      );

throws Trace: Cannot read property 'rootNode' of undefined

on this fixture 🤔 I'm a little stumped at the moment.

command:
  actionName: swap
  partialTargets:
    - type: primitive
      transformation:
        type: containingScope
        scopeType: namedFunction
    - type: primitive
      transformation:
        type: containingScope
        scopeType: ifStatement
      mark:
        type: decoratedSymbol
        symbolColor: blue
        character: i
  extraArgs: []
languageId: python
decorations:
  blue.i:
    start:
      line: 5
      character: 0
    end:
      line: 5
      character: 2
initialState:
  document: |
    import sys

    def hello_world(name="pokey"):
        print(f"hello, {name}")
      
    if __name__ == "__main__":
        hello_world(sys.argv[0])
  selections:
    - active:
        line: 2
        character: 20
      anchor:
        line: 2
        character: 20
  visibleRanges:
    - start:
        line: 0
        character: 0
      end:
        line: 7
        character: 0
  clipboard: ""
finalState:
  document: |
    import sys

    if __name__ == "__main__":
        hello_world(sys.argv[0])
      
    def hello_world(name="pokey"):
        print(f"hello, {name}")
  selections:
    - active:
        line: 2
        character: 20
      anchor:
        line: 2
        character: 20
  visibleRanges:
    - start:
        line: 0
        character: 0
      end:
        line: 7
        character: 0
  clipboard: ""

pokey

Nice!!

For that test that's not working, it's possible that the rootNode can't be found because the syntax tree extension is not getting a chance to create a syntax tree? Easiest thing would be to try an async sleep (eg await sleep(500)) right after you open the document. You might also check what that URI is that gets passed into the Location. Problem could be that it's an "anonymous" doc. Might see if the way of loading up the fixture from my link in comment works any better

pokey · 2021-07-12T10:58:22Z

src/test/suite/recorded.test.ts

+        fixture.initialState.selections.map(deserializeSelection);
+
+      // TODO restore visible ranges?
+      // Not sure of a straightforward way to do this. Maybe just use to test folding?


Used to test folding and scrolling; we can leave it for now

pokey · 2021-07-12T11:17:54Z

src/TestCase.ts

+      document: activeEditor.document.getText(),
+      selections: activeEditor.selections.map(serializeSelection),
+      visibleRanges: activeEditor.visibleRanges.map(serializeRange),
+      clipboard: await vscode.env.clipboard.readText(),


I'd be tempted to only bother with the clipboard if it's a copy or paste command

pokey · 2021-07-12T11:18:43Z

src/TestCase.ts

+    const keys: string[] = [];
+    targets.forEach((target) => {
+      if (target.mark.type === "decoratedSymbol") {
+        keys.push(`${target.mark.symbolColor}.${target.mark.character}`);


I would try to use the function in navigation map for this so that we don't duplicate the key generation here

pokey · 2021-07-12T11:20:42Z

src/TestCase.ts

+
+type Command = {
+  actionName: ActionType;
+  partialTargets: PartialTarget[];


For completeness I'd be tempted to also capture the full target, even if we don't end up using it for anything

pokey · 2021-07-12T11:21:09Z

src/TestCase.ts

+  return { line: position.line, character: position.character };
+}
+
+type Command = {


It would be cool to capture the talon command. I wonder if we could use something like keeper to have talon automatically send it over. Tho fwiw I think keeper may be broken with recent talon? Been getting error messages with it

pokey · 2021-07-12T11:29:47Z

src/test/suite/processTargets.test.ts

@@ -8,7 +8,7 @@ import processTargets from "../../processTargets";
 import { Target, Token } from "../../Types";
 // import * as myExtension from '../../extension';

-suite("processTargets", () => {
+suite.skip("processTargets", () => {


pokey · 2021-07-12T11:32:26Z

src/test/suite/recorded.test.ts

+    __dirname,
+    // TODO What's the best way to handle this?
+    "../../../src/test/suite/recordings"
+  );


not saying this is better or worse than what you have here, but here's one approach that I had bookmarked in case helpful

pokey · 2021-07-12T11:33:50Z

src/test/suite/recorded.test.ts

+      // TODO restore visible ranges?
+      // Not sure of a straightforward way to do this. Maybe just use to test folding?
+
+      const navigationMap = new NavigationMap();


See above comment; if we can get away with it it may be worth just asserting that the map matches for the tokens we care about and then hopefully the assert doesn't fail

pokey · 2021-07-12T11:34:38Z

src/test/suite/recorded.test.ts

+          editor: vscode.window.activeTextEditor!,
+        };
+        const [color, character] = key.split(".");
+        // @ts-ignore TODO should probably add a decoration color type?


not sure I follow; there is a token decoration color type

pokey · 2021-07-12T11:35:00Z

src/test/suite/recorded.test.ts

+      });
+      const editor = await vscode.window.showTextDocument(document);
+
+      await vscode.env.clipboard.writeText(fixture.initialState.clipboard);


I'd prefer to use a mock for this, so that we don't overwrite the real clipboard

brxck · 2021-07-12T15:37:43Z

Thanks @pokey, exactly what I needed to keep this going!

pokey · 2021-07-12T15:43:17Z

Thanks @pokey, exactly what I needed to keep this going!

Awesome! btw feel free to ping me on slack if you'd like when you post something in case I miss the email 😊. Always excited to see progress

pokey

Alright cool stuff! Left a bunch of comments. As mentioned below something feels slightly off about the TestCase recording setup, but tough to tell with the file so big so let's extract some pieces to separate files and have another look. I think it's getting close; the meat of the code looks really good it's just some top-level restructuring that might need to happen which should be quick using vscode's refactoring tools

pokey · 2021-07-22T22:03:36Z

src/TestCase.ts

+    return targetedDecorations;
+  }
+
+  isThatMarkTargeted() {


This won't work if a "that" mark is in a compound target, right? I think you need to descend like you do for finding decorated marks

pokey · 2021-07-22T22:09:34Z

src/NavigationMap.ts

+  public serializeRanges() {
+    const rangeMap: { [coloredSymbol: string]: SerializedRange } = {};
+    Object.entries(this.map).forEach(([key, value]) => {
+      rangeMap[key] = serializeRange(value.range);
+    });
+    return rangeMap;
+  }


What is this for? Don't you just serialize the targets that actually get referred to?

pokey · 2021-07-22T22:18:03Z

src/TestCase.ts

+    };
+  }
+
+  async getSnapshot(): Promise<TestCaseSnapshot> {


I think it's a bit confusing to have both this function and the static one

pokey · 2021-07-22T22:40:29Z

src/TestCase.ts

+  returnValue: any;
+};
+
+export default class TestCase {


Something doesn't quite feel right here but it's tough to see everything with all the functions in this file. Maybe let's split things up a bit to get a better feel?

pokey · 2021-07-22T22:40:47Z

src/TestCase.ts

+    this.context = context;
+  }
+
+  extractPrimitiveTargetKeys(...targets: PrimitiveTarget[]) {


I'd get all these primitive target extraction functions into another file

pokey · 2021-07-22T22:50:22Z

src/test/suite/recorded.test.ts

+      assert.deepStrictEqual(fixture.finalState, resultState);
+      assert.deepStrictEqual(fixture.returnValue, returnValue);
+
+      sinon.restore();


Per above, let's put this in a teardown func

pokey · 2021-07-22T22:51:15Z

src/test/suite/recorded.test.ts

+        cursorlessApi.thatMark.get()
+      );
+      assert.deepStrictEqual(fixture.finalState, resultState);
+      assert.deepStrictEqual(fixture.returnValue, returnValue);


As mentioned above, we'll not include properties in the fixture that aren't relevant, eg clipboard, so we can avoid checking them if not necessary

pokey · 2021-07-22T22:51:36Z

src/test/suite/recorded.test.ts

+      }
+
+      let clip = fixture.initialState.clipboard;
+      sinon.replace(Clipboard, "readText", async () => clip);


maybe only mock if clipboard is in fixture

pokey · 2021-07-22T22:52:14Z

testFixtures/chuckThat.yml

+  thatMark:
+    - active:
+        line: 2
+        character: 0
+      anchor:
+        line: 2
+        character: 0


Is this the correct thatMark? This test didn't work for me

🤔 it is, I just checked.

pokey · 2021-07-22T22:53:15Z

testFixtures/swap.yml

+      anchor:
+        line: 7
+        character: 0
+  visibleRanges: []


visible ranges broke for me here, but as mentioned we can just leave this property out and not check for it if it's not there

also, we should prob raise an exception in setup if they include visible ranges, because I don't think we properly support it yet

Don't define irrelevant fixture properties Extract test case helpers Remove navigation map serializer Clarify test case methods

pokey

This is beautiful. Gotten super crisp. I left a dozen minor nits. I'm happy to knock them out but if you get to them first feel free to take them down

pokey · 2021-07-27T21:13:12Z

src/TestCase.ts

+    const excludableFields = {
+      clipboard: !["copy", "paste"].includes(this.command.actionName),
+      thatMark:
+        this.initialState == null &&


Not immediately obvious to me why we check whether initialState is null here

Yeah looking at this I have to think about it too, maybe I can clarify the code.

If we are taking the first snapshot, then we only want to record thatMark when it is targeted. If we're taking the final snapshot, we always want to record thatMark.

Yeah I figured that out later; I'd just pass something into the function?

pokey · 2021-07-27T21:16:09Z

src/TestCase.ts

+    );
+  }
+
+  async recordFinalState(returnValue: unknown) {


Why unknown instead of any here? Tbh I don't really know the difference 😅

It's basically like a type safe any. You can use unknown in the same places you would use any, but it requires you to assert a type if you want to do anything with it.

pokey · 2021-07-27T21:17:30Z

src/TestCase.ts

+    const workspacePath = vscode.workspace.workspaceFolders?.[0].uri.path;
+    let document;
+
+    if (workspacePath && filename) {


So are you assuming that the user is recording in the cursorless workspace?

Yeah, wasn't really sure how to handle this. I wasn't assuming we were in the cursorless workspace, and that's why I moved fixtures from src/test/suite/fixtures/recorded to a folder in the root.

Now that I'm thinking about it, I could actually check if we're in the cursorless workspace or not. If we're not in the cursorless workspace, just show the yaml in a pane?

Yeah that sounds good to me

Btw I'm happy to call this out of scope but from a usability standpoint I think my ideal sequence would be:

Ask user for talon command

Wait for them to run command

Have subfolders in the fixture directory and present them with a list of possible subdirectories and allow them to select "add new" if they type something that doesn't exist

Ask them for a file name

Display a message that the fixture was made, with a link to open it, but don't open it by default

Note that steps 3–5 only happen if in cursorless workspace

So then what we'd do is to have a command in talon "record", which will grab the parsed command, call record on cursorless, type in literal command, then issue command. So workflow is then:

Open a file to test on. We might consider storing a few common ones somewhere

Say "record take air"

Select subdirectory

Say test name

Reset file and repeat

Should be able to rapidly record dozens of tests the way. Alternately, we could keep things as they are extension side but ask for dir and name before asking for talon command. Then we'd have two record commands. The first one is eg "setup recording" and the second is "record". So you'd say

"setup recording in named ", which would call extension record and fill out dir and name

"record take air", which would type in "take air" literally, then issue the command

Maybe the second approach is better?

pokey · 2021-07-27T21:30:57Z

src/extension.ts

+      testCaseRecorder.filename = filename ?? "";
+      testCaseRecorder.talonCommand = talonCommand ?? "";


I'd be tempted to use null / undefined if they don't answer, but prob not a big deal

pokey · 2021-07-27T21:34:41Z

src/extractTargetedMarks.ts

+  if (!navigationMap) {
+    return {};
+  }


When does this happen?

I don't think it actually does, but that's how it's typed due to the way the extension sets up on activation.

Hmm but the type signature of function doesn't allow undefined or null right?

pokey · 2021-07-27T21:50:27Z

src/test/suite/recorded.test.ts

+      }
+
+      // Wait for cursorless to set up decorations
+      await new Promise((resolve) => setTimeout(resolve, 300));


Hmm. We might wanna figure out how to remove this delay when we get 50+ test cases but prob fine for now

Yeah, I haven't played with the timeout, it could probably be lower. Maybe we add a function/property to see if decorations are finished that we can check periodically?

Let's leave it for now. They run pretty quick. If it becomes a problem we can do something fancier

pokey · 2021-07-27T21:51:29Z

src/test/suite/recorded.test.ts

+
+      // Assert that recorded decorations are present
+      Object.entries(fixture.marks).forEach(([key, _]) => {
+        const [color, character] = key.split(".") as [SymbolColor, string];


As above, I'd let navigationMap own this logic

pokey · 2021-07-27T21:52:06Z

src/test/suite/recorded.test.ts

+      Object.entries(fixture.marks).forEach(([key, _]) => {
+        const [color, character] = key.split(".") as [SymbolColor, string];
+        const token = cursorlessApi.navigationMap.getToken(color, character);
+        assert(token != null, `Mark "${color} ${character}" not found`);


We should assert that this token (serialised) is equal to the serialised token, no?

pokey · 2021-07-27T21:53:48Z

src/test/suite/recorded.test.ts

+        ...fixture.command.extraArgs
+      );
+
+      // Do not assert visible ranges; for now they are included as context


We should prob be a bit louder about this and link an issue

pokey · 2021-07-27T22:08:42Z

testFixtures/chuckThat.yml

+        type: that
+  extraArgs: []
+languageId: python
+targets:


I think I might call this fullTargets or inferredFullTargets? We might add a docstring to that field as well to indicate it's just for why-nots right now. Also maybe let's move this one to the end; looks like the order gets preserved when dumping

Tbh I'm tempted to remove it because it adds a big chunk to an otherwise quite compact test case format, but I'm very much on the fence

Added a comment and moved it to the end. Should be easy to remove if we decide it's not worth keeping.

pokey · 2021-07-27T23:10:27Z

And one more minor one: for location of the yaml files, I'd be inclined to use src/test/suite/fixtures/recorded. Does that make sense?

brxck · 2021-07-28T15:11:16Z

I hit most of these. I'll see about the recording flow and fixture location later today!

brxck · 2021-07-30T05:09:46Z

@pokey Moved the fixtures and took a shot at the recording flow you described:

Ask user for talon command

Wait for them to run command

Have subfolders in the fixture directory and present them with a list of possible subdirectories and allow them to select "add new" if they type something that doesn't exist

Ask them for a file name

Display a message that the fixture was made, with a link to open it, but don't open it by default

Note that steps 3–5 only happen if in cursorless workspace

pokey · 2021-07-30T06:03:16Z

Nice! Will have one last look tomorrow and get it merged in

Fwiw I am planning to make the following quick changes tomorrow before merging:

Add an env var that indicates cursorless workspace dir. This env var will be set when you run in debug mode. Then if the var is set it will behave the same as if you're in cursorless workspace. This behaviour will make it trivial to add tests while you're developing a new feature.
Implement flow style for the full target output to make things more compact
Implement flow style for simple objects to make more compact
have another look at order of keys in yaml

My goal is to have:

super compact and readable output for ease of reviewing test cases
rapid effortless test case recording for new and old features

I'm planning to sit down for a bit tomorrow and will try to knock these out myself. But if I don't, I think I may just file some of them and merge in this PR without.

If you get a chance before I do feel free to take a swing but I'll hopefully get a good chunk of time tomorrow

AndreasArvidsson · 2021-08-01T02:17:32Z

May I suggest one improvement? Using "pre:phrase" event you can just send the spoken form to cursorless instead of having to type it. If you also use the spoken form as the file name we can skip that step and actually do bulk recordings.

"cursorless record"
popup to chose directory
take air => file created
clear bat => file created
"record stop"

Here is my preliminary implementation
cursorless-dev/cursorless-talon#46
#169

@pokey @brxck

pokey mentioned this pull request Jul 9, 2021

Test case recorder #64

Closed

brxck force-pushed the test-case-recorder-59 branch from 5d7c5ae to 12098d6 Compare July 10, 2021 23:37

pokey reviewed Jul 12, 2021

View reviewed changes

pokey and others added 15 commits July 13, 2021 22:31

Very preliminary steps

f7587e3

Write test case info to file

815e829

Save only target decorations

ed4ee0d

Don't use yaml refs in test case fixtures

3d0e8b0

Record clipboard contents in snapshots

e9b60e4

Run recorded test cases

efb696c

Only save clipboard contents in copy/paste actions

e95a993

Reuse navigation map key creation

b06f27f

Add inferred full targets to fixture

c51def0

Move test fixtures from src to root

cc0e4bf

Remove setting up navigation map

9d65fde

Attempt to mock clipboard (and fail)

fa52794

Add navigationMap to graph

35a8ce5

Attempt to mock navigation map construction

0471c7f

Store "that mark" in test case fixture

09a743f

brxck force-pushed the test-case-recorder-59 branch from 12098d6 to 09a743f Compare July 15, 2021 14:38

brxck added 3 commits July 16, 2021 20:08

Check nav map and improve that mark handling

43a4473

Give up for the night lol

829882d

Support testing that mark

087c7fd

brxck marked this pull request as ready for review July 18, 2021 23:49

AndreasArvidsson linked an issue Jul 21, 2021 that may be closed by this pull request

Make test case recorder #59

Closed

2 tasks

pokey reviewed Jul 22, 2021

View reviewed changes

brxck added 2 commits July 26, 2021 20:18

Start refactoring test cases

ca334b2

Don't define irrelevant fixture properties Extract test case helpers Remove navigation map serializer Clarify test case methods

Fix that mark detection on compound targets

01b8553

pokey reviewed Jul 27, 2021

View reviewed changes

brxck added 6 commits July 28, 2021 08:09

Improve navigation map handling

c5c3d9b

Clarify thatMark exclusion conditions

060d91d

Rename fixture fields

08ebc6b

Rephrase 'serialize' as 'to plain object'

076da28

Add issue for visible range testing

52f4408

Revert makeGraph export change

ff6a1e1

brxck added 3 commits July 29, 2021 20:04

Improve fixture writing and move directory

f585de0

Add test case folder selection

b8df923

Create test case recorder class

decc22f

brxck force-pushed the test-case-recorder-59 branch from f278cc8 to decc22f Compare July 30, 2021 04:45

brxck added 2 commits July 29, 2021 22:00

Ask for fixture directory after recording

16f67bb

Move file handling to test case recorder

0b8df41

pokey added 4 commits July 30, 2021 18:51

Cleanup

3f188a3

More cleanup

a255e0b

cleanup

8ce8f86

swap anchor with active

39d62f5

pokey approved these changes Jul 31, 2021

View reviewed changes

pokey merged commit 3e617af into cursorless-dev:master Jul 31, 2021

pokey mentioned this pull request Aug 6, 2021

Switch to flow-style for simple objects in test yaml dump #161

Closed

		testCaseRecorder.filename = filename ?? "";
		testCaseRecorder.talonCommand = talonCommand ?? "";

Test Case Recorder #87

Test Case Recorder #87

Conversation

brxck commented Jul 8, 2021 • edited Loading

pokey commented Jul 8, 2021

brxck commented Jul 8, 2021

pokey commented Jul 8, 2021 • edited Loading

pokey commented Jul 8, 2021

pokey commented Jul 8, 2021

brxck commented Jul 10, 2021

pokey left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pokey Jul 12, 2021 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pokey Jul 12, 2021 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

brxck commented Jul 12, 2021

pokey commented Jul 12, 2021

pokey left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pokey left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pokey Jul 27, 2021 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pokey commented Jul 27, 2021

brxck commented Jul 28, 2021

brxck commented Jul 30, 2021

pokey commented Jul 30, 2021 • edited Loading

AndreasArvidsson commented Aug 1, 2021 • edited Loading

brxck commented Jul 8, 2021 •

edited

Loading

pokey commented Jul 8, 2021 •

edited

Loading

pokey left a comment •

edited

Loading

pokey Jul 12, 2021 •

edited

Loading

pokey Jul 12, 2021 •

edited

Loading

pokey left a comment •

edited

Loading

pokey Jul 27, 2021 •

edited

Loading

pokey commented Jul 30, 2021 •

edited

Loading

AndreasArvidsson commented Aug 1, 2021 •

edited

Loading