loadFixtures.ts 5.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179
  1. /* global __dirname */
  2. /* eslint import/no-nodejs-modules:0 */
  3. import fs from 'fs';
  4. import path from 'path';
  5. import TestStubFixtures from '../../../fixtures/js-stubs/types';
  6. const FIXTURES_ROOT = path.join(__dirname, '../../../fixtures');
  7. type Options = {
  8. /**
  9. * Flatten all fixtures to together into a single object
  10. */
  11. flatten?: boolean;
  12. };
  13. /**
  14. * Loads a directory of fixtures. Supports js and json fixtures.
  15. */
  16. export function loadFixtures(dir: string, opts: Options = {}): TestStubFixtures {
  17. const from = path.join(FIXTURES_ROOT, dir);
  18. const files = fs.readdirSync(from);
  19. // @ts-expect-error, this is a partial definition
  20. const fixtures: TestStubFixtures = {};
  21. for (const file of files) {
  22. const filePath = path.join(from, file);
  23. if (/[jt]sx?$/.test(file)) {
  24. const module = require(filePath);
  25. if (module.default) {
  26. throw new Error('Javascript fixtures cannot use default export');
  27. }
  28. fixtures[file] = module;
  29. continue;
  30. }
  31. if (/json$/.test(file)) {
  32. fixtures[file] = JSON.parse(fs.readFileSync(filePath).toString());
  33. continue;
  34. }
  35. throw new Error(`Invalid fixture type found: ${file}`);
  36. }
  37. if (opts.flatten) {
  38. // @ts-expect-error, this is a partial definition
  39. const flattenedFixtures: TestStubFixtures = {};
  40. for (const moduleKey in fixtures) {
  41. for (const moduleExport in fixtures[moduleKey]) {
  42. // Check if our flattenedFixtures already contains a key with the same export.
  43. // If it does, we want to throw and make sure that we dont silently override the fixtures.
  44. if (flattenedFixtures?.[moduleKey]?.[moduleExport]) {
  45. throw new Error(
  46. `Flatten will override module ${flattenedFixtures[moduleKey]} with ${fixtures[moduleKey][moduleExport]}`
  47. );
  48. }
  49. flattenedFixtures[moduleExport] = fixtures[moduleKey][moduleExport];
  50. }
  51. }
  52. return flattenedFixtures;
  53. }
  54. return fixtures;
  55. }
  56. const extensions = ['.js', '.ts', '.tsx', '.json'];
  57. // This is a mapping of special cases where fixture name does not map 1:1 to file name.
  58. // Some fixture files also contain more than one fixture so additional mappings are needed.
  59. // If you have added new fixtures and you are seeing an error being throw, please add the fixture
  60. const SPECIAL_MAPPING = {
  61. AllAuthenticators: 'authenticators',
  62. OrgRoleList: 'roleList',
  63. BitbucketIntegrationConfig: 'integrationListDirectory',
  64. DiscoverSavedQuery: 'discover',
  65. Entries123Base: 'entries',
  66. Entries123Target: 'entries',
  67. Events: 'events',
  68. EventsStats: 'events',
  69. EventStacktraceMessage: 'eventStacktraceException',
  70. GitHubIntegration: 'githubIntegration',
  71. GitHubIntegrationConfig: 'integrationListDirectory',
  72. GitHubIntegrationProvider: 'githubIntegrationProvider',
  73. MetricsField: 'metrics',
  74. MetricsSessionUserCountByStatusByRelease: 'metrics',
  75. MetricsTotalCountByReleaseIn24h: 'metrics',
  76. MOCK_RESP_VERBOSE: 'ruleConditions',
  77. OrgOwnedApps: 'integrationListDirectory',
  78. OutcomesWithReason: 'outcomes',
  79. PluginListConfig: 'integrationListDirectory',
  80. ProviderList: 'integrationListDirectory',
  81. PublishedApps: 'integrationListDirectory',
  82. SentryAppComponentAsync: 'sentryAppComponent',
  83. SentryAppInstalls: 'integrationListDirectory',
  84. SessionsField: 'sessions',
  85. SessionStatusCountByProjectInPeriod: 'sessions',
  86. SessionStatusCountByReleaseInPeriod: 'sessions',
  87. SessionUserCountByStatus: 'sessions',
  88. SessionUserCountByStatusByRelease: 'sessions',
  89. TagValues: 'tagvalues',
  90. VercelProvider: 'vercelIntegration',
  91. };
  92. function tryRequire(dir: string, name: string): any {
  93. if (SPECIAL_MAPPING[name]) {
  94. return require(path.resolve(dir, SPECIAL_MAPPING[name]));
  95. }
  96. for (const ext of extensions) {
  97. try {
  98. return require(path.resolve(dir, lowercaseFirst(name) + ext));
  99. } catch {
  100. // ignore
  101. }
  102. }
  103. throw new Error('Failed to resolve file');
  104. }
  105. function lowercaseFirst(value: string): string {
  106. return value.charAt(0).toLowerCase() + value.slice(1);
  107. }
  108. export function makeLazyFixtures<UserProvidedFixtures extends Record<any, any>>(
  109. fixturesDirectoryPath: string,
  110. userProvidedFixtures: UserProvidedFixtures
  111. ): TestStubFixtures & UserProvidedFixtures {
  112. const lazyFixtures = new Proxy(
  113. {},
  114. {
  115. get(target, prop: string) {
  116. if (target[prop]) {
  117. return target[prop];
  118. }
  119. if (userProvidedFixtures[prop]) {
  120. return userProvidedFixtures[prop];
  121. }
  122. try {
  123. const maybeModule = tryRequire(fixturesDirectoryPath, prop);
  124. for (const exportKey in maybeModule) {
  125. target[exportKey] = maybeModule[exportKey];
  126. }
  127. } catch (error) {
  128. return () => {
  129. throw new Error(
  130. error +
  131. '\n\n' +
  132. `Failed to resolve ${prop} fixture.
  133. - Your fixture does not map directly to file on disk or fixture file could be exporting > 1 fixture.
  134. - To resolve this, add a mapping to SPECIAL_MAPPING in loadFixtures.ts or ensure fixture export name maps to the file on disk.
  135. - If you are seeing this only in CI and you have followed the step above, check the exact casing of the file as it is case sensitive.
  136. `
  137. );
  138. };
  139. }
  140. if (target[prop] === undefined) {
  141. return () => {
  142. throw new Error(
  143. `Failed to resolve ${prop} fixture.
  144. - Your fixture does not map directly to file on disk or fixture file could be exporting > 1 fixture.
  145. - To resolve this, add a mapping to SPECIAL_MAPPING in loadFixtures.ts or ensure fixture export name maps to the file on disk.
  146. - If you are seeing this only in CI and you have followed the step above, check the exact casing of the file as it is case sensitive.`
  147. );
  148. };
  149. }
  150. return target[prop];
  151. },
  152. }
  153. );
  154. return lazyFixtures as TestStubFixtures & UserProvidedFixtures;
  155. }