utils-code/jesseduffield.lazygit
1
0
Fork 0
mirror of https://github.com/jesseduffield/lazygit.git synced 2026-09-10 23:56:24 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity
jesseduffield.lazygit/pkg/integration/tests/sync
History
Stefan Haller 19d0048cc4 More explicit test of status panel content 
Use Equals instead of Contains for asserting the status view content. This
solves the problem that we might assert Contains("↓2 repo"), but what it really
shows is "↑1↓2 repo", and the test still succeeds. At best this is confusing.

Also, this way we don't have to use the awkward DoesNotContain to check that it
really doesn't show a checkmark.

To do this, we need to fix two whitespace problems:
- there was always a space at the end for no reason. Simply remove it. It was
  added in efb51eee96, but from looking at that diff it seems it was added
  accidentally.
- there was a space at the beginning if the branch status was empty. This is
  actually a cosmetic problem, for branches without a status the text was
  indented by once space. Change this so that the space is added conditionally.
  It's a bit awkward that we have to use Decolorise here, but this will go away
  again later in this branch.
2024-06-03 13:02:46 +02:00
..
fetch_prune.go Construct arg vector manually rather than parse string 2023-05-23 19:49:19 +10:00
fetch_when_sorted_by_date.go Keep same branch selected when refreshing branches 2024-01-19 09:25:07 +01:00
force_push.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
force_push_multiple_matching.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
force_push_multiple_upstream.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
force_push_remote_branch_not_stored_locally.go Add integration test for pushing when the remote is not stored locally 2024-06-01 08:12:45 +02:00
force_push_triangular.go Correctly request force-pushing in triangular workflows 2024-05-19 09:44:38 +02:00
pull.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
pull_and_set_upstream.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
pull_merge.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
pull_merge_conflict.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
pull_rebase.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
pull_rebase_conflict.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
pull_rebase_interactive_conflict.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
pull_rebase_interactive_conflict_drop.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
push.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
push_and_auto_set_upstream.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
push_and_set_upstream.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
push_follow_tags.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
push_no_follow_tags.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
push_tag.go Use sentence case everywhere 2023-05-25 23:52:19 +10:00
push_with_credential_prompt.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00
rename_branch_and_pull.go Use sentence case everywhere 2023-05-25 23:52:19 +10:00
shared.go More explicit test of status panel content 2024-06-03 13:02:46 +02:00