└── README.md
/README.md:
--------------------------------------------------------------------------------
1 | # CulebraTester-public
2 |
3 |
4 | | ⚠️ Warning |
5 | |:----------|
6 | | A new version of this project using Kotlin can be found at https://github.com/dtmilano/CulebraTester2-public |
7 |
8 | This is a public repository corresponding to [CulebraTester](https://github.com/dtmilano/CulebraTester) to be able to handle public issues.
9 |
10 | Android testing can be complicated, time-consuming, and tedious. What if it didn’t have to be?
11 |
12 | **CulebraTester** provides a real-time point and click test recording through a web browser. This browser is connected to the Android device under test and the generated source code can be directly imported into Android Studio and run as a normal test.
13 |
14 |
15 | # Issues
16 | - [Public issues](https://github.com/dtmilano/CulebraTester-public/issues)
17 | - [Private issues](https://github.com/dtmilano/CulebraTester/issues) (only for those with write access to the private repo)
18 |
19 | ## Report an issue
20 | | Important |
21 | |:----------|
22 | |Before reporting an issue, search the existing one in [Public issues](https://github.com/dtmilano/CulebraTester-public/issues) and if the same issues was already reported add comments to it.|
23 |
24 | Need to report a technical issue or send feedback about **CulebraTester**? If so, follow these steps:
25 |
26 | 1. On the browser click **Send Feedback** -> **Bug Report**
27 | 2. Copy and paste the generated test into a new issue or as a comment of an existing one
28 | 3. If you'd like to include additional information in your report, such as a URL, a screenshot, javascript console output, adb logcat or an attachment, by dragging & dropping, *Choose Files selecting them*, or pasting from the clipboard. If you are reporting an issue about a specific generated file, please attach any relevant non-confidential documents to the report.
29 |
30 | ### Template
31 | The generated template will contain some information about your device (i.e. build number) if you don't want to share all that info you can use the following template.
32 |
33 | ```
34 | # [Enter short bug description here]
35 |
36 | [Enter detailed bug description here]
37 | ## Repro Steps
38 |
39 | 1. [First Step]
40 | 2. [Second Step]
41 | 3. [and so on...]
42 |
43 | ## Expected
44 |
45 | [Enter expected behavior here]
46 | ## Actual
47 |
48 | [Enter actual behavior here]
49 | ### Debug Info
50 |
51 |