Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions HANDSON0.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,3 +5,5 @@ The following are prerequisites for this workshop:
1. Look into your internal infosec policies and make sure you can let CloudBees process your source code during this workshop. Note we do not store your source code, nor are they used to train any AI models. See [data privacy and protection policy](https://www.launchableinc.com/docs/resources/policies/data-privacy-and-protection/) for more details.

1. You need a computer with `git`, `python3`, and `java` installed.

1. Prepare a repository that contains test code where you want to try PTS. We recommend using a repository you normally work with. (You will not need to push any code during the hands-on.)
13 changes: 13 additions & 0 deletions HANDSON1.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,19 @@ You can install it with pip:
pip3 install --upgrade launchable~=1.0
```

> [!TIP]
> If you encounter `externally managed error`
> <details>
>
> Try installing `pipx` and use it.
> see: https://pipx.pypa.io/stable/installation/
>
> ```
> pipx install launchable~=1.0
> ```
> </details>


Let’s check that it’s installed correctly:

```
Expand Down
15 changes: 5 additions & 10 deletions HANDSON2.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ Along the way, you will learn the major concepts of Smart Test.
To experiment with Smart Tests, first, let's clone your repository locally.
How to do this depends on your project.

If you already cloned repository, please skip cloning the repository and move to the repo directory.

```
git clone ...
cd your/repository
Expand Down Expand Up @@ -45,15 +47,8 @@ Visit https://app.launchableinc.com/organizations/<ORG>/workspaces/<WORKSPACE>/d
What just happened? Smart Tests recorded the current HEAD of your local repository as the build,
using the name given.

By default, this command looks at the current directory.
If you have multiple repositories, you'll use the `--source` option to direct the command to the right repositories.

```
launchable record build --name mychange1 --source app=path/to/repo1 --source test=path/to/repo2 ...
```

In the above example, you are telling Smart Tests that the build consists of two repositories: `app` and `test`.

>[!NOTE]
> If you have multiple repositories, please check [this document](https://www.launchableinc.com/docs/sending-data-to-launchable/using-the-launchable-cli/recording-builds-with-the-launchable-cli/recording-builds-from-multiple-repositories/) to let Smart Tests know that the build consists of your repositories.


Since this was the first time you recorded a build, Smart Tests needed to transfer relatively
Expand All @@ -77,7 +72,7 @@ Now, let's have Smart Tests select the best set of tests to run for this test se

```
launchable subset --session $(cat session.txt) --get-tests-from-guess file > subset.txt
cat subset.txt
less subset.txt
```

Since you haven't run any tests yet, Smart Tests will select files in your repository
Expand Down