issues
search
robotframework
/
statuschecker
Tool for validating that executed Robot Framework test cases have expected statuses and log messages.
26
stars
9
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Tests fail with robotframework 7.0
#46
dotlambda
opened
7 months ago
0
Allow for user controlled or raw regular expression
#45
emanlove
opened
10 months ago
4
RF 6.1 support
#44
aaltat
closed
1 year ago
1
Rf 61 support
#43
aaltat
closed
1 year ago
0
Add Flake8 compelxity check
#42
aaltat
closed
1 year ago
0
Use Black with Python 3.7
#41
aaltat
closed
1 year ago
0
Support RF 5 and 6
#40
aaltat
closed
1 year ago
0
Add support for counting messages
#39
aaltat
closed
1 year ago
0
Add support counting messages.
#38
aaltat
closed
1 year ago
0
fix skip status support
#37
ericbjones
opened
2 years ago
0
Support RF 4 style SKIP
#36
aaltat
closed
2 years ago
1
support rf4 skip status
#35
ericbjones
closed
2 years ago
1
Use linting
#34
aaltat
closed
2 years ago
13
Wild card support for log verification
#33
yahman72
closed
2 years ago
25
Wildcard support for the log verification
#32
yahman72
closed
2 years ago
5
"FAIL GLOB" fails if patternt contains "-"
#31
mint-user
closed
3 years ago
4
latest statuschecker processing output.xml from 4.0.1 (probably also from 4.0.0) will strip sourcename attribute
#30
rasjani
closed
3 years ago
4
Revert changes in release 2.0.2, it causes too much other failures
#29
aaltat
closed
3 years ago
1
Keywords teardown in RF 3 could be accessed without TEARDOWN marker
#28
aaltat
closed
3 years ago
0
Fixed bug when accessing keywords in teardown when not marked as teardown
#27
aaltat
closed
3 years ago
0
statuschecker works different with different RF versions
#26
aaltat
closed
3 years ago
0
Fix RF 3.2 regression
#25
aaltat
closed
3 years ago
0
Use RF4.0.1 in CI
#24
aaltat
closed
3 years ago
0
Use 4.0.1b1 in CI
#23
aaltat
closed
3 years ago
0
Rf4 0 support part2
#22
aaltat
closed
3 years ago
0
Add SETUP and TEARDOWN markers for checking logs from test setup and teardown
#21
aaltat
closed
3 years ago
0
Setup and teardown marker
#20
aaltat
closed
3 years ago
0
Drop Python 2 support
#19
aaltat
closed
3 years ago
0
In RF 4 do not use deprecated keywords attribute.
#18
aaltat
closed
3 years ago
0
Revert RF 4.0 support because it does not work
#17
aaltat
closed
3 years ago
0
Add pypy3 in CI
#16
aaltat
closed
3 years ago
0
Fix RF install
#15
aaltat
closed
3 years ago
0
Drop Python 2 support and use Python 3.6 is minimum version.
#14
aaltat
closed
3 years ago
0
For RF4 use body instead of keyword attribute
#13
aaltat
closed
3 years ago
0
Add GitHub actions
#12
aaltat
closed
3 years ago
0
Broken with RF4
#11
mkorpela
closed
3 years ago
0
Console logging for statuschecker
#10
HaaiHenkie
opened
4 years ago
3
Use of robotstatuschecker with --prerebotmodifier option
#9
HaaiHenkie
opened
4 years ago
0
Add support for ERROR level
#8
aaltat
closed
5 years ago
0
Robot logger.error(''Message") is not supported by statuschecker
#7
aaltat
closed
5 years ago
1
Take `rellu` into use to ease creating releases
#6
pekkaklarck
closed
3 years ago
1
Allow test case status and log status to be different
#5
joaonc
opened
5 years ago
3
Validating message with FAIL level fails if test itself passes
#4
joaonc
opened
5 years ago
8
Can't install with Ubuntu - NameError: name 'sys_platform' is not defined
#3
chevi
closed
7 years ago
5
Python 3 compatibility
#2
pekkaklarck
closed
8 years ago
1
Python3 Compatibility: added parentheses to prints
#1
stasiek
closed
8 years ago
6