issues
search
SeasideSt
/
Parasol
Testing web apps in Smalltalk using Selenium WebDriver.
MIT License
31
stars
16
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
separated parasol and seaside
#18
noha
closed
5 years ago
10
Baselinefixes: explicit dependency on Seaside3 not in Gemstone
#17
jbrichau
closed
6 years ago
0
Update selenium and chromedriver + pharo7 builds are not allowed to fail
#16
jbrichau
closed
6 years ago
0
Fix for #14
#15
pdebruic
closed
5 years ago
9
Unexpected response status code 302 while creating web driver session.
#14
pdebruic
closed
5 years ago
3
waitUntil on BPSeasideWebDriverTestCase
#13
LesageYann
opened
6 years ago
1
The #getCapabilities method is broken with selenium v3.6.0
#12
Rinzwind
closed
5 years ago
2
Caching mechanism for drivers does not reset cookies
#11
Rinzwind
opened
7 years ago
0
Loading in Squeak fails with error “Name not found: Grease-Core”
#10
Rinzwind
closed
7 years ago
3
Filetree repository directory contains metadata files
#9
Rinzwind
closed
1 year ago
0
Automated tests are not run for VisualWorks
#8
Rinzwind
closed
7 years ago
1
Parasol test framework has no support for dealing with random test failures
#7
jecisc
opened
7 years ago
1
The Seaside development toolbar is not automatically hidden when running tests
#6
jecisc
opened
7 years ago
3
Gemstone fixes
#5
jbrichau
closed
7 years ago
2
Add the possibility to customize a component to test before the tests
#4
jecisc
closed
2 years ago
7
Would be cool to be able to initialize the state of a component at the beginning of a test case.
#3
jecisc
closed
1 year ago
2
Parasol self-tests fail randomly
#2
Rinzwind
opened
7 years ago
3
POST /session/56...73/keys did not match a known command
#1
jgfoster
closed
7 years ago
2
Previous