## Critical User Journey 6: Connect an implementation or test to a function
**Job To Be Done**
When <situation> I want to <job> so I can <expected outcome or motivation>
**Acceptance criteria**
An editor user...
* [ ] Should be able to find a function from the Wikifunctions landing page and navigate to it
* [ ] Should be able to clearly visualize its attached or detached implementations and testers
* [ ] Should be able to safely attach available implementations of testers that are still detached
* [ ] Should be able to safely detach any attached implementations of testers
---
##Completion checklist
//During the review process, edit and check these items to reflect the completion status of this epic//
* **Functionality**
* [ ] Every project (repository) involved in this user story has its separate Phabricator task
* [ ] Every related task should passes its completion checklist
* [ ] The tests for every involved project pass successfully
* [ ] The build process for every involved project passes successfully
* [ ] Coverage for every involved project has improved or stayed the same
* **Design**
* [ ] Design review on updated software
* [ ] Test concept via an Alpha, Beta or Prototype with partner communities and those potentially impacted by feature, in their preferred language
* **Documentation**
* [ ] Has related and updated documentation, E.g.:
* Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc)
* Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on MediaWiki extension pages.
* Product or model changes: should have related documentation updated in meta
* **Versioning**
* [ ] If changes in submodule packages are involved, every project that uses this submodule has updated submodule version and passes tests and build