Build acceptance test for pricing.search
See original GitHub issueIn order to effectively use the no missing translations test, we need to make sure that every page is visited during acceptance tests.
This issue tracks the missing pricing.search
acceptance test
for ember new commers the value some.route
is the route that’s missing you can find them under router.js
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Acceptance Testing: A Step-By-Step Guide - Functionize
Acceptance testing is a testing technique performed to determine whether or not the software system has met the required specifications.
Read more >Acceptance Testing Documentation With Real Time Scenarios
Documents play a major role in Acceptance testing and any ... to be tested: Basic functionalities (Example: Search by different keywords, ...
Read more >What Are Acceptance Test and why They Matter - Semaphore CI
Acceptance testing is the practice of running high-level, end-to-end tests to ensure that a system follows spec. Acceptance tests are ...
Read more >What is acceptance testing and do you really need to do it?
Yes, you really do need to do acceptance testing, whether it's simple beta testing or more than that. Here's the how and why....
Read more >UAT User Acceptance Test - how to do it right - Usersnap
First, make sure it's easy for users to submit feedback. Find a tool that works within your UAT environment so that users do...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@emadehsan I haven’t tested it in CouchDB 2 so it is possible it doesn’t work right now. I think in general for our upcoming 1.0 release we need to back away from CouchDB 2 as there are other issues with using it right now.
@baoqchau sure feel free to work on this. As far as testing, you need to navigate to the module you are testing as the search is context sensitive to which module you are currently on. So to testing pricing, you need to navigate to /pricing and then put a value in the search text box at the top of the navigation pane and then click on the magnifying glass to execute the search. Does that make sense?