Skip to content

Conversation

@abacaphiliac
Copy link
Contributor

  • update feature-generator in integration-test to return json-object with all required keys and appropriate variation-structures.
  • update APC integration test to verify value is baz after setting baz directly into redis (i believe this was a problem in earlier versions as well).
  • add required monolog dependency to integration test composer config.

…th all required keys and appropriate variation-structures. update APC integration test to verify value is baz after setting baz directly into redis (i believe this was a problem in v1.0.0 as well).
# cached value so not updated
$redis->hset("launchdarkly:features", 'foo', $this->gen_feature("foo", "baz"));
$this->assertEquals("bar", $client->variation('foo', $user, 'jim'));
$this->assertEquals("baz", $client->variation('foo', $user, 'jim'));
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, i now know that this change is not acceptable. i'm having trouble understanding why it seems to be necessary in my vagrant test-suite. closing this merge request. i'll focus on getting the integration tests to run in CI instead.

@abacaphiliac
Copy link
Contributor Author

closing because i know the value change from bar to baz is not acceptable.

LaunchDarklyCI pushed a commit that referenced this pull request Jan 3, 2020
don't let user fall outside of last bucket in rollout
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant