You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(results): Add refresh rate to results model
For consistency, refresh rate is added to the DeviceSpecs property of the TestCaseResult and AveragedTestCaseResult
chore(test): update snapshots
refactor: remove unneeded changes
Copy file name to clipboardExpand all lines: packages/commands/measure/src/__tests__/__snapshots__/measure.test.tsx.snap
+8-14Lines changed: 8 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -12,19 +12,16 @@ Time taken to run the test.
12
12
Can be helpful to measure Time To Interactive of your app, if the test is checking app start for instance.
13
13
Average FPS
14
14
60 FPS
15
-
Frame Per Second. Your app should display
16
-
60
17
-
Frames Per Second to give an impression of fluidity. This number should be close to
18
-
60
19
-
, otherwise it will seem laggy.
15
+
Frame Per Second. Your app should display 60 Frames Per Second to give an impression of fluidity. This number should be close to 60, otherwise it will seem laggy.
16
+
20
17
See
21
18
22
19
this video
23
20
24
21
for more details
25
22
Average CPU usage
26
23
83 %
27
-
An app might run at 60FPS but might be using too much processing power, so it's important to check CPU usage.
24
+
An app might run at high frame rates, such as 60 FPS or higher, but might be using too much processing power, so it's important to check CPU usage.
28
25
Depending on the device, this value can go up to
29
26
100% x number of cores
30
27
. For instance, a Samsung A10s has 4 cores, so the max value would be 400%.
@@ -859,7 +856,7 @@ exports[`flashlight measure interactive it displays measures: Web app with measu
859
856
<div
860
857
class="text-neutral-400 text-sm"
861
858
>
862
-
An app might run at 60FPS but might be using too much processing power, so it's important to check CPU usage.
859
+
An app might run at high frame rates, such as 60 FPS or higher, but might be using too much processing power, so it's important to check CPU usage.
863
860
<br />
864
861
Depending on the device, this value can go up to
865
862
<code>
@@ -3816,19 +3813,16 @@ Time taken to run the test.
3816
3813
Can be helpful to measure Time To Interactive of your app, if the test is checking app start for instance.
3817
3814
Average FPS
3818
3815
-
3819
-
Frame Per Second. Your app should display
3820
-
60
3821
-
Frames Per Second to give an impression of fluidity. This number should be close to
3822
-
60
3823
-
, otherwise it will seem laggy.
3816
+
Frame Per Second. Your app should display 60 Frames Per Second to give an impression of fluidity. This number should be close to 60, otherwise it will seem laggy.
3817
+
3824
3818
See
3825
3819
3826
3820
this video
3827
3821
3828
3822
for more details
3829
3823
Average CPU usage
3830
3824
-
3831
-
An app might run at 60FPS but might be using too much processing power, so it's important to check CPU usage.
3825
+
An app might run at high frame rates, such as 60 FPS or higher, but might be using too much processing power, so it's important to check CPU usage.
3832
3826
Depending on the device, this value can go up to
3833
3827
100% x number of cores
3834
3828
. For instance, a Samsung A10s has 4 cores, so the max value would be 400%.
@@ -4226,7 +4220,7 @@ exports[`flashlight measure interactive it displays measures: Web app with no me
4226
4220
<div
4227
4221
class="text-neutral-400 text-sm"
4228
4222
>
4229
-
An app might run at 60FPS but might be using too much processing power, so it's important to check CPU usage.
4223
+
An app might run at high frame rates, such as 60 FPS or higher, but might be using too much processing power, so it's important to check CPU usage.
0 commit comments