ppcano

import { check, sleep } from 'k6';
import http from 'k6/http';

export let options = {
  vus: 50,
  duration: "3s"
};

export default function() {
  let res = http.get("https://test.k6.io/");

ppcano

├── Product
    ├──Open Source
    ├──Cloud
    ├──Pricing
    ├──Unit testing for performance
    ├──Integrations
├── Resources
 ├──k6 docs

ppcano

import { check, sleep } from 'k6';
import http from 'k6/http';

export let options = {
  duration: "1m",
  vus: 100
}

export default function() {
      let res;

ppcano

import { sleep } from "k6";
import http from "k6/http";

export let options = {
  duration: "1m",
  vus: 50,
  thresholds: {
    http_req_duration: ["p(95)<500"]
  }
};

ppcano

import http from "k6/http";
import { sleep } from "k6";

export let options = {
  duration: '45s',
  thresholds: {
    "http_req_duration": ["p(99)<500"]
  }
};

ppcano

import {sleep} from "k6";
import mainPageUserFlow from "../cases/main-page";
import billingUserFlow from "../cases/billing";

export let options = {
  thresholds: {
    "group_duration{group:::mainPageGroup}": ["p(99)<300"],
    "group_duration{group:::billingGroup}": ["p(99)<300"]
  }
};

ppcano

diff --git i/lib/broccoli/default-packager.js w/lib/broccoli/default-packager.js
index 1228226ee..af184f6db 100644
--- i/lib/broccoli/default-packager.js
+++ w/lib/broccoli/default-packager.js
@@ -845,46 +845,33 @@ module.exports = class DefaultPackager {
         annotation: 'Tests To Process',
       });
 
-
       if (this.isModuleUnificationEnabled) {

ppcano

diff --git i/lib/models/addon.js w/lib/models/addon.js
index 2f9de9d00..1734e3604 100644
--- i/lib/models/addon.js
+++ w/lib/models/addon.js
@@ -298,6 +298,10 @@ let addonProto = {
       public: 'public',
     };
 
+    if (this.isModuleUnification()) {
+      this.treePaths.styles = 'src/ui/styles';

ppcano

I have reviewed the ember-octane-blueprint project and I have some thoughts that I would like to share:

The ember-octane-blueprint duplicates code from the ember-cli/module-unification-app blueprint; If we want to create tests for the ember-octane-blueprint project, we may end up duplicating the existing MU tests and having to maintain two similar MU app blueprints.

I wonder if a better strategy would be to figure out how the octane-blueprint project could reuse the existing module-unification-app blueprint.

ppcano

import Ember from 'ember';
import layout from '../templates/components/other-template';


export default Ember.Component.extend({
  layout
});