Add replication steps to readme.

Author: chrissimon-au

README.md

@@ -1,71 +1,10 @@
 # score-e2e-test-bug-replication README
 
-This is the README for your extension "score-e2e-test-bug-replication". After writing up a brief description, we recommend including the following sections.
+This repo replicates a bug lodged here: https://github.com/microsoft/vscode/issues/178184
 
-## Features
+Hover sequences are different at runtime vs testtime.
 
-Describe specific features of your extension including screenshots of your extension in action. Image paths are relative to this README file.
+To demonstrate:
 
-For example if there is an image subfolder under your extension project workspace:
-
-\!\[feature X\]\(images/feature-x.png\)
-
-> Tip: Many popular extensions utilize animations. This is an excellent way to show off your extension! We recommend short, focused animations that are easy to follow.
-
-## Requirements
-
-If you have any requirements or dependencies, add a section describing those and how to install and configure them.
-
-## Extension Settings
-
-Include if your extension adds any VS Code settings through the `contributes.configuration` extension point.
-
-For example:
-
-This extension contributes the following settings:
-
-* `myExtension.enable`: Enable/disable this extension.
-* `myExtension.thing`: Set to `blah` to do something.
-
-## Known Issues
-
-Calling out known issues can help limit users opening duplicate issues against your extension.
-
-## Release Notes
-
-Users appreciate release notes as you update your extension.
-
-### 1.0.0
-
-Initial release of ...
-
-### 1.0.1
-
-Fixed issue #.
-
-### 1.1.0
-
-Added features X, Y, and Z.
-
----
-
-## Following extension guidelines
-
-Ensure that you've read through the extensions guidelines and follow the best practices for creating your extension.
-
-* [Extension Guidelines](https://code.visualstudio.com/api/references/extension-guidelines)
-
-## Working with Markdown
-
-You can author your README using Visual Studio Code. Here are some useful editor keyboard shortcuts:
-
-* Split the editor (`Cmd+\` on macOS or `Ctrl+\` on Windows and Linux).
-* Toggle preview (`Shift+Cmd+V` on macOS or `Shift+Ctrl+V` on Windows and Linux).
-* Press `Ctrl+Space` (Windows, Linux, macOS) to see a list of Markdown snippets.
-
-## For more information
-
-* [Visual Studio Code's Markdown Support](http://code.visualstudio.com/docs/languages/markdown)
-* [Markdown Syntax Reference](https://help.github.com/articles/markdown-basics/)
-
-**Enjoy!**
+1. Run this extension in extensionHost using F5.  Open the `src/extension.ts` file and hover over the method name `activate`.  You should see the typescript hover information and as `Hello!` message at the bottom, this is as expected.
+1. Run the extension tests.  The tests will fail as the first hover result contains `Hello` - however this should be last, as it is visually in the UI.

src/test/suite/extension.test.ts

@@ -1,6 +1,5 @@
 import * as assert from 'assert';
 import * as path from 'path';
-import * as util from 'node:util';
 // You can import and use all API from the 'vscode' module
 // as well as import your extension to test it
 import * as vscode from 'vscode';
@@ -30,7 +29,7 @@ suite('Hover Test Suits', () => {
 		const hoverTexts = hoverResults.map(h => (h.contents[0] as vscode.MarkdownString).value)
 
 		console.log(hoverTexts);
-		
+
 		assert.equal(hoverTexts.length, 2);
 		assert.match(hoverTexts[0], /activate/); // the typescript `activate` hover content should be first
 		assert.match(hoverTexts[1], /Hello/); // the 'hello' hover content should be last