End-to-End Export Testing [Timebox]
See original GitHub issueThis task is to do end-to-end testing for exports - the goal is to make and document the API calls for the following types of exports. The result of this task is to document the API call made in this issue - e.g. what does the POST
call to exports look like?
Export types to test:
- RGB export
- false-color composite
- export all bands
- NDVI export
- NDWI export
- EVI Export
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Timeboxing: The Ultimate Strategy to Skyrocket Productivity
When your session ends, mark off one Pomodoro and record what you ... the timeboxing method, here are a few tried and tested...
Read more >Iteration Planning - TechDocs
The purpose of the iteration planning meeting is for the team to commit to the completion of a set of the highest-ranked product...
Read more >How do we Manage Bugs in Agile? - Anca Onuta - Medium
Learn how successful Agile Teams handle the bugs with Agile methodologies to be predictable and deliver customer value with their products.
Read more >Chapter 13: Timeboxing - Agile Business Consortium
Timeboxing is one of DSDM's key practices. DSDM defines a Timebox as a fixed period of time, at the end of which an...
Read more >What is a Timebox? - Agile Alliance
The critical rule of timeboxed work is that work should stop at the end of the timebox, and review progress: has the goal...
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 FreeTop 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
Top GitHub Comments
Results, Part 1
Some results of exports testing.
Issues realted to export (https://github.com/azavea/raster-foundry/pull/1920, https://github.com/azavea/raster-foundry/issues/1925) and import (https://github.com/azavea/raster-foundry/pull/1899, https://github.com/azavea/raster-foundry/pull/1903) were discovered during the test process, however all in all export routes work as expected and RGB export definitely works.
Export all bands
Is not supported. In the current implementation RAW export would be done if there would be no color correction settings. Right now it’s not possible to delete / reset color correction settings, it means that all exports work in RGB / false-color composite modes.
NDVI, NDWI, EVI export
No supported as well, as AST Export doesn’t support projects. Though in the postman query dump (WARN: headers information should be changed as it’s unique and required for auth) a query with a try to make AST export is done, though never finished succesfull.
RGB export / false-color composite
URLs used:
Current WEB UI:
POST Query:
Response:
Default RGB:
POST Query:
Response:
Custom color correction:
Custom Correction POST Query:
Exports POST query:
Response
All preset colors (Urban, Water, Natural Color, Vegetation & water, Bare Earth change detection, Atmosphere penetration, Forest Fire, Agriculture) work fine as well, as it’s a sepcial case of the thing above, however testing of them was done as well, and can be reproduced using the postman query dump (WARN: headers information should be changed as it’s unique and required for auth).
The whole process works well: WEBUI => Airflow => EMR (emr step experience some permission issues, though it can be only my personal issue)
Results, Part 3 (Part 1 extension)
Addition to show that false color export works.
Urban Color correction:
Color Correction POST Query:
Exports POST query:
Response